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

With no annotations provided, the description carries the full burden. It states only the core parse action and does not disclose that all parameters except 'url' are ignored/discarded, nor does it describe error behavior or return format.

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 wasted words. It communicates the essential purpose 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?

With nine optional parameters and no output schema, the description leaves critical ambiguity: which parameter to use, what the return shape is, and how invalid URLs are handled. This is not enough for reliable invocation without further inference.

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?

Although every parameter has a schema description, those descriptions are generic and misleading (e.g., 'url' is described as 'normalize or cite' rather than 'GitHub URL to parse'). The tool description does not clarify which parameter is the GitHub URL, and the other eight parameters appear irrelevant and discarded.

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'), identifies the exact resource ('GitHub URL'), and states the output ('owner and repo'). This clearly differentiates the tool from sibling URL/shape tools.

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?

No explicit guidance is given for when to use this tool over alternatives such as normalize-url, figma-url-shape, or jira-key-shape. The description implies use for GitHub URLs but does not state exclusivity or alternatives.

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