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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with this. It adds the output scope (profile and badge URLs) but does not disclose return structure, error behavior, or any rate limits; not a contradiction.

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?

Single sentence, front-loads the action and input, with no filler. Every word adds value.

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 one-parameter, read-only lookup the description conveys the essential workflow: input handle, output profile/badge URLs. It is adequate but lacks explicit differentiation from sibling tools and any details about output format or failure modes.

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?

The schema provides only 'handle' as a string with no description (0% coverage). The description compensates by identifying the handle as a GitHub handle and as the input to resolve, giving the parameter a meaningful semantic role.

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?

States a specific action 'Resolve' with a clear resource ('GitHub handle' to 'Chapa profile and badge URLs'). It is self-contained but does not explicitly distinguish itself from siblings like get_impact_profile or verify_badge.

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's use case—when you have a GitHub handle and need profile/badge URLs—but gives no explicit 'when to use' vs alternatives. No exclusions or comparison with sibling tools are provided.

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