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

No annotations are provided, so the description must carry the behavioral burden. The verb 'parse' signals a non-mutating local operation, but the description does not disclose what happens for malformed GitHub URLs, whether a network request is avoided, or that unrelated schema fields are ignored. Adequate for a simple parser, but with gaps.

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 filler, front-loaded with the verb and resource. Every word earns its place.

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 the description never states the return shape, failure behavior, or how the nine optional parameters should be supplied. For an agent selecting among many sibling tools, this is too sparse.

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 coverage is 100%, so the baseline is 3; every property has a description. However, the main description adds no parameter semantics, and with unrelated fields like city, feed, json, and zone present, it does not explicitly tell the agent that only url is relevant for GitHub owner/repo extraction.

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'), a concrete resource ('a GitHub URL'), and names the intended result ('owner and repo'). This is enough to distinguish it from sibling shape tools like figma-url-shape or domain-shape without needing alternatives named.

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 choose this tool instead of normalize-url, browser-url-ok, or the other URL/shape siblings. A 'Parse owner and repo' statement implies an obvious use case, but the absence of alternatives or conditions leaves the agent to infer routing.

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