Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare the tool read-only and non-destructive, so the description only needs to add context beyond that. It adds the useful qualifier 'public', implying these profiles are accessible without special credentials, but it does not disclose potential limitations, error conditions, or what happens if one handle is invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no filler or repetition. It front-loads the core action and resource, though its brevity edges into under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and minimal parameter documentation, the description fails to explain what the comparison returns, what criteria are compared, or any behavioral expectations. An agent could call the tool with two handles, but it would have little idea what result to expect or how to interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for explaining the parameters. It indirectly maps 'handle' and 'other_handle' to the 'two public Chapa impact profiles', but it does not explain what a handle is, how it should be formatted, or any constraints, leaving room for incorrect invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action, 'Compare', and a specific resource, 'two public Chapa impact profiles', making the basic function clear. It is distinguishable from siblings like get_impact_profile and find_profile because it explicitly involves comparing two profiles rather than retrieving one, though it does not detail what aspects are compared.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool versus alternatives such as get_impact_profile or find_profile. The usage context is only implied by the phrase 'Compare two...' and no exclusions or conditions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.