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

With no annotations, the description carries the full burden, but it only says 'Parse' and does not disclose whether the tool validates URL shape, returns an error for non-GitHub URLs, or what the parsed output looks like. The schema's many 'discarded' parameter descriptions hint at shape-check behavior that the description never explains.

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 with no filler. It is appropriately concise for a simple parse operation, though it could have spent one more clause on output or required input without hurting clarity.

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, yet the description only covers the basic purpose. It does not state which parameter to pass, what is returned, or how invalid/non-GitHub URLs are handled, making it insufficient for reliable invocation.

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%, so the baseline is 3, and the description does not add param-level meaning. It ties the operation to a GitHub URL but never identifies `url` as the key parameter (whose schema description is the generic 'HTTPS URL to normalize or cite'), leaving agents to infer the mapping among nine optional parameters.

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 resource ('owner and repo from a GitHub URL'), making the core function clear and differentiating it from sibling shape tools aimed at Figma, Jira, or domains. It does not explicitly mention the validation/shape-check behavior implied by the tool name, so it falls short of a 5.

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 usage is implied: call this when you need owner/repo from a GitHub URL. However, there is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives, and no statement about prerequisites like requiring a valid GitHub URL.

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