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

With no annotations, the description carries the burden of disclosing side effects and failure behavior. The verb 'parse' implies a pure local operation, but the description never explicitly states that no network access occurs, how invalid URLs are handled, or whether the operation is side-effect free. Schema notes like 'no disk access' apply only to unrelated parameters.

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 focused sentence with no filler or redundant wording. It is front-loaded and easy for an agent to scan.

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?

The tool has nine optional parameters, no output schema, and no annotations, but the description only provides a one-line purpose. It omits required input specification, output format, error behavior, and selection context, leaving an agent without enough information to invoke the tool confidently.

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?

Although schema description coverage is 100%, the parameter descriptions are generic and appear copied from other tools (e.g., 'HTTPS URL to normalize or cite', 'City name for a public weather hint'). The description does not clarify that `url` is the relevant parameter, whether other parameters are ignored, or why there are nine optional fields with no required field.

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 uses a specific verb ('parse') and identifies the exact resource ('owner and repo') and source ('GitHub URL'), making the tool's core purpose immediately clear and distinguishing it from sibling URL and shape tools.

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 on when to use this tool instead of alternatives such as normalize-url, domain-shape, or figma-url-shape. The description states only what the tool does, not when it should be chosen.

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