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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Parse owner and repo' and does not explain return format, failure behavior, whether network access occurs, or how the tool handles non-GitHub or malformed URLs. The schema's references to values being 'discarded after the shape check' suggest more complex behavior than the description reveals.

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 one tight, front-loaded sentence with no filler. However, it is so terse that it omits essential operational details, so it earns a 4 rather than a 5.

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?

Given a 9-parameter schema with zero required parameters and no output schema or annotations, this description is incomplete. It does not say which parameter carries the GitHub URL, what the parsed owner/repo result looks like, or whether the other described inputs are ignored or rejected.

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 GitHub-specific meaning of the URL, but it does not identify which of the 9 optional parameters should be used, why most parameters are irrelevant, or that additionalProperties false prevents passing owner/repo as direct fields. This leaves real ambiguity for parameter selection.

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 names a specific verb ('Parse') and a specific resource ('owner and repo') from a 'GitHub URL', which clearly distinguishes this from sibling shape tools like jira-key-shape, figma-url-shape, and domain-shape. Even without additional context, an agent can tell what operation this tool performs and on what input.

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 about when to use this tool versus siblings such as normalize-url, browser-url-ok, or other shape checkers. The description implies usage only via the phrase 'GitHub URL', but it does not state exclusions, prerequisites, or alternatives.

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