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

No annotations are provided, so the description must carry the burden. It only says 'Parse owner and repo', leaving unknown whether it performs validation, what it does with the other 8 parameters, or what the output looks like. The schema's parameter descriptions hint at discarding inputs, but the tool description itself doesn't disclose this.

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, front-loaded sentence that avoids redundancy. Every word contributes to the core purpose, making it concise and easy to scan.

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 9 optional parameters, no output schema, and no annotations, this one-sentence description is insufficient. It doesn't explain return values, how the tool behaves with unrelated inputs, or whether there are any side effects. Given the complexity, the description is incomplete.

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 baseline is 3. The description adds that the URL should be a GitHub URL, but it does not clarify why the other 8 parameters (ref, city, feed, host, json, path, zone, query) exist or how they relate to the parsing purpose. The description slightly enhances the url parameter's meaning but leaves others ambiguous.

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 verb ('Parse') and a precise resource ('owner and repo from a GitHub URL'), and this clearly distinguishes it from sibling shape tools like domain-shape or figma-url-shape. An agent can immediately understand what this tool does.

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 provides no guidance on when to use this tool versus alternatives, no exclusions, and no mention of cases where another tool would be better. It only states the core action without context of competing tools.

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