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

With no annotations, the description carries the full burden of behavioral disclosure, and it only promises a parse operation. It does not reveal the return shape, error behavior for non-GitHub URLs, or that several accepted parameters are discarded after the call. The 'discarded' details live only in the schema, not in the description.

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 sentence with no filler, and the core action is front-loaded. It is appropriately brief, though slightly under-specified given the complexity of the schema.

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?

No annotations, no output schema, 9 parameters with none required, and a description that only states the core parse. The agent is not told which parameter to populate, what the result looks like, or whether irrelevant parameters are ignored. This is not enough for reliable invocation.

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?

All 9 parameters have schema descriptions, so the baseline is 3. The description adds the useful clarification that `url` should be a GitHub URL and that owner/repo are the extracted result, which the generic url schema description misses. However, it does not explain which of the other 8 parameters are relevant or required, so it does not exceed the baseline.

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'), so an agent immediately knows the tool's function. This clearly distinguishes it from sibling shape tools like figma-url-shape or jira-key-shape. No vague or tautological language.

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 implies the obvious trigger—when a GitHub URL needs to be reduced to owner/repo—but it never explicitly says 'use this when...' nor contrasts it with alternatives like normalize-url or web-fetch. There are no prerequisites or exclusions stated, so guidance is inferred rather than explicit.

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