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

No annotations are provided, so the description carries the full disclosure burden. It claims to 'parse owner and repo' but the schema reveals that 8 of 9 parameters are discarded, implying a validate-and-discard behavior rather than a retrieval that returns owner/repo. The description neither confirms what the tool returns nor that non-GitHub URLs fail, so its implied behavior is misleading relative to the schema.

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, tightly front-loaded sentence with zero filler. Every word earns its place and the core purpose is stated immediately.

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 is far more complex than the description suggests: it accepts nine parameters, discards eight, and has no output schema to clarify return values. The description explains only the url case and never addresses why the other parameters are accepted, what happens on invalid input, or what the tool returns. For a shape-check tool of this complexity, this is inadequate.

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 adds the key semantic that the url parameter is the GitHub URL to parse, which is useful. However, it sheds no light on why eight unrelated parameters (city, zone, json, query, etc.) exist on a 'GitHub repo' tool, leaving those semantics confusing.

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?

States a specific verb (parse) and resource (owner and repo from a GitHub URL), which distinguishes it from sibling shape-checkers like figma-url-shape or domain-shape. However, it reads as a pure parsing tool, while the schema's pervasive 'discarded' language implies it is actually a validation/shape-check tool, so the stated purpose slightly undersells its real role.

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?

Provides no guidance on when to choose this tool over the many sibling URL/shape tools (domain-shape, figma-url-shape, jira-key-shape, browser-url-ok). An agent must infer that this is specifically for GitHub URLs, with no explicit when-to-use or when-not-to-use framing.

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