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

With no annotations, the description is the sole source. 'Parse' implies a read-only operation with no side effects, but this is not explicitly stated. The lack of detail about error handling or network access leaves some ambiguity, but the nature of parsing suggests low risk.

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 concise sentence with no redundancy or unnecessary detail. It is perfectly sized for the minimal information it conveys.

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?

The description omits critical information: the expected input parameter (likely 'url'), the output format (owner and repo as separate fields or an object?), and error behavior for invalid URLs. Without these, a user cannot reliably use the tool without additional inspection.

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?

The description does not explain any parameters, and the schema descriptions are generic or misleading (e.g., 'url' is described as 'HTTPS URL to normalize or cite' rather than for parsing owner/repo). The presence of many unrelated parameters (city, feed, path, etc.) is confusing, and the description offers no clarification about which parameter is relevant.

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 clearly states a specific action ('Parse owner and repo') and a specific resource ('GitHub URL'), making the purpose understandable. It does not explicitly differentiate from sibling shape tools, but the mention of GitHub distinguishes it.

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?

No guidance is provided on when to use this tool vs alternatives, nor any mention of context or conditions. The description only states what it does, leaving the user to infer appropriate usage.

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