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

No annotations are provided, so the description carries the full behavioral burden. It only says 'Parse owner and repo' and does not disclose failure behavior, output format, side effects, or what happens with malformed or non-GitHub URLs. The schema descriptions mention that some values are 'discarded after the shape check,' but the tool description itself adds no behavioral context.

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. Every word contributes to the core purpose. It is appropriately concise for a simple parsing tool, though it sacrifices completeness for brevity.

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 9 parameters, no annotations, and no output schema, this description is incomplete. It does not state which parameter should receive the GitHub URL, what the parsed owner/repo result looks like, how errors are handled, or whether the other parameters are ignored or rejected. An agent would need to infer too much from the generic schema.

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 the important context that the URL is a GitHub URL and that owner/repo are extracted, but it does not clarify which of the 9 parameters is actually relevant, nor does it explain how the other parameters relate to this tool. The description adds some meaning beyond the schema but does not fully disambiguate the parameter set.

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 verb and resource: 'Parse owner and repo from a GitHub URL.' This clearly explains what the tool does and the domain of input. However, it does not explicitly differentiate it from sibling tools like normalize-url, domain-shape, or figma-url-shape, so it is clear but not fully distinguished.

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?

There is no guidance about when to use this tool versus alternatives such as normalize-url or figma-url-shape. The description implies the use case of a GitHub URL, but it does not state exclusions, prerequisites, or scenarios where another sibling tool would be preferred.

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