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

With no annotations, the description carries the full burden but only says 'Parse.' It does not disclose return format, behavior on invalid URLs, or that the many other schema parameters are discarded or ignored. The schema hints at 'discarded after...' behavior, but the description itself adds little transparency.

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, tight sentence with no filler and a front-loaded verb. However, it may be undersized given the schema's nine parameters and lack of annotations.

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?

There is no output schema and no annotations, so this one-liner is insufficient for correct invocation. It does not explain how the owner/repo result is returned, what counts as a valid GitHub URL, or why the schema includes unrelated fields like city, feed, host, json, path, zone, and query.

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 of 3 applies even though the description adds no parameter-level detail. The description implies owner/repo as an outcome, but does not clarify which of the nine parameters is the GitHub URL or reconcile with the schema's 'url' description of 'normalize or cite.'

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 action ('Parse') and outcome ('owner and repo'), scoped to 'a GitHub URL.' This distinguishes it from sibling tools like figma-url-shape and jira-key-shape. It does not, however, clarify the broader 'shape' behavior suggested by the tool name.

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 phrase 'from a GitHub URL' gives an implied usage context, so an agent could infer it is for GitHub URLs rather than other URL types. There is no explicit when-to-use guidance, no mention of alternatives, and no exclusion criteria.

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