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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Parse' and gives no indication of return format, failure behavior on non-GitHub URLs, normalization behavior, or the fact that many input fields are discarded. The schema's discard notes are structured-field context, not description value.

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 sentence with no filler, and the core action is front-loaded. It earns its place and is appropriately sized for the stated purpose.

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?

Given the tool has 9 optional parameters, no annotations, and no output schema, this description is materially incomplete. It does not state what the parsed result looks like, which parameter to populate, or how invalid inputs are handled, leaving an agent with significant gaps for correct 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 coverage is 100%, so the baseline is 3. The description adds useful meaning by implying the 'url' parameter should receive a GitHub URL, but it does not explain which of the nine optional parameters matters or how the eight unrelated parameters relate to the tool. No strong adjustment is warranted.

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 states a specific action ('Parse') with a specific resource ('owner and repo') and a specific source ('GitHub URL'). This clearly distinguishes it from sibling shape tools like figma-url-shape and jira-key-shape. The unusually broad input schema creates some ambiguity, but the stated purpose itself is precise.

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 use case is implied: call this when you have a GitHub URL and need owner/repo extracted. However, the description does not state when not to use it or point to alternatives such as normalize-url or domain-shape, leaving routing to the agent's inference.

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