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

Annotations already indicate this is read-only and non-destructive, so the safety profile is covered. The description adds useful context by noting the profiles are 'public' and that the comparison focuses on badge headlines. It does not describe return format, ordering, or what happens when profiles are not found, but that is less critical given the read-only annotation.

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 one concise sentence with no filler. The action and resource are front-loaded, and the comparison criterion is appended efficiently. Every word earns its place.

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?

For a simple two-parameter read-only tool, the description is serviceable but leaves gaps. It does not explain what the returned comparison looks like, and since there is no output schema, some behavioral disclosure about return values would be helpful. The 'headline each badge draws' phrase hints at the output but does not fully specify 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 the undocumented handle and other_handle parameters. The phrase 'two public Chapa impact profiles' weakly implies both parameters are profile identifiers, but it does not clarify handle format, whether order matters, or what valid values look like. This is a meaningful gap for a tool with no parameter documentation.

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 clearly states the action ('Compare'), the resource ('two public Chapa impact profiles'), and the specific criterion ('by the headline each badge draws'). This distinguishes it from sibling tools like get_impact_profile or find_profile, which retrieve rather than compare. The phrase 'headline each badge draws' is a bit idiosyncratic but does not obscure the core purpose.

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?

The description implies the tool is for comparing two profiles rather than retrieving one, which is a clear context. However, it does not explicitly state when to prefer this over alternatives such as get_impact_profile or verify_badge, nor does it mention any exclusions or prerequisites. The usage guidance is implied rather than explicit.

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