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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only states the core parsing action but does not disclose that most of the 9 schema parameters (city, feed, json, etc.) are irrelevant and ignored, nor does it mention behavior on invalid URLs or return format. This is a significant transparency gap.

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 extraneous words, front-loading the action. It is concise and well-structured, though perhaps too terse to convey important context.

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?

With 9 parameters, no output schema, and no annotations, the description is far too incomplete. It does not specify which parameters are used, what the tool returns, or how it handles invalid URLs. An agent would be unable to confidently invoke it correctly based on this description alone.

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%, but the descriptions are generic and some conflict with the tool's purpose—e.g., the 'url' parameter is described as 'HTTPS URL to normalize or cite' rather than a GitHub URL. The tool description does not clarify which parameters are actually used, and the mismatch between schema and purpose reduces clarity.

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 differentiates it from sibling tools like domain-shape or figma-url-shape, as it names the GitHub context. The purpose is unambiguous, though the output format is not stated.

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 on when to use this tool versus alternatives. It does not say 'use this when you have a GitHub URL' nor does it mention any exclusions. Given the large sibling set with similar shape tools, some usage direction would be expected.

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