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

No annotations are provided, and the description does not disclose side effects, output format, or what happens with the many irrelevant parameters. While 'parse' implies read-only behavior, the description does not clarify whether other inputs are ignored or rejected, and it omits any mention of error handling.

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, front-loaded sentence that immediately conveys the primary purpose. It is concise and easy to read, though it omits necessary context about the extra parameters and expected behavior.

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 9 optional parameters and no output schema, yet the description explains neither the return value format nor how to combine parameters. It does not mention whether all parameters are accepted or only url is used, leaving the agent without enough context to invoke it correctly in ambiguous cases.

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 100%, but the main description implies only 'url' is relevant, while the schema lists many unrelated fields. The url parameter description says 'HTTPS URL to normalize or cite' rather than 'GitHub URL to parse owner and repo,' which conflicts with the tool's stated purpose. Additional descriptions do not clarify how or whether they relate to parsing a GitHub repo.

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 core action ('Parse owner and repo from a GitHub URL') with a specific verb and resource, and the tool name distinguishes it from sibling shape tools. However, the input schema contains many unrelated parameters (city, feed, json, etc.), which creates confusion about the actual scope.

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 gives no guidance on when to use this tool versus alternatives like normalize-url, domain-shape, or figma-url-shape. It does not state that it is specifically for GitHub repo URLs or what to do when the URL is not a GitHub URL.

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