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

The word 'parse' suggests a read-only operation, and some property descriptions mention 'discarded' or 'no disk access.' However, the tool description itself does not clearly state side effects, data retention, or whether network access may occur.

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 main description is a single, focused sentence with no unnecessary words. Property descriptions are also terse and consistently one line each.

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?

There is no output schema, no return-format description, and no error-behavior guidance. The tool has nine optional parameters with many unrelated fields, so the description does not provide enough context for an agent to invoke it 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?

Every parameter has a one-line description, but most are irrelevant to parsing a GitHub URL (e.g., city, feed, zone, query), and the url parameter is described generically as 'normalize or cite' rather than as a GitHub URL. With no required parameters, it is unclear which field the agent should actually pass.

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 a specific action ('Parse owner and repo') and a specific resource ('GitHub URL'). It also distinguishes this tool from sibling URL/shape tools such as normalize-url and figma-url-shape.

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 phrase 'from a GitHub URL' implies the intended use case, but there is no explicit guidance about when to prefer this tool over similar siblings or when not to use it. No alternatives are mentioned.

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