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

The word 'parse' suggests a read-only, side-effect-free operation, and the schema's 'discarded' notes reinforce that. However, no annotations are provided, and the description does not disclose behavior on invalid URLs, non-GitHub URLs, or the structure of the parsed result. It adds minimal behavioral context beyond the obvious.

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?

A single, front-loaded sentence with no filler. Every word earns its place, and the core purpose is immediately clear.

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?

For a simple parse tool the description is functionally adequate, but with no output schema and no annotations it leaves the agent without the return format or error behavior. The large number of unrelated parameters could also confuse an agent, and the description does not say that only 'url' matters. The schema partially covers this, but the overall context is not fully complete.

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. The description clarifies that the 'url' parameter is a GitHub URL and that owner/repo are extracted from it, but it adds no guidance on the other eight parameters, several of which are unrelated to GitHub URL parsing. The schema already marks them as discarded, so the description contributes little beyond that.

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 ('GitHub URL') and names the exact output ('owner and repo'). This clearly distinguishes it from sibling shape tools like figma-url-shape or jira-key-shape, which target different URL formats.

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 does not state when to use this tool versus alternatives. With 26 sibling tools, including other shape tools (domain-shape, figma-url-shape, jira-key-shape), there is no guidance such as 'use for GitHub URLs only' or 'use domain-shape for generic hostnames.' The usage context is only implied by the tool name, not stated.

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