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

The description says 'parse', implying read-only behavior, but this is never stated explicitly. Several parameter descriptions mention 'discarded' values, hinting at no side effects, yet there is no explanation of what is returned, whether the call fails on non-GitHub URLs, or what 'shape check' means.

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 itself is concise—one short sentence—with no filler. However, it is so under-specified relative to the large and heterogeneous schema that the brevity becomes a liability rather than a strength.

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 tool description omits crucial context: what output is produced, what parameters are actually required, what happens with the unused parameters, and what constitutes a valid input. Given the conflicting schema, an agent cannot reliably call this tool.

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?

Each parameter has a description, but they are generic and mostly unrelated to GitHub repo parsing. For example, 'city' is described as a weather hint and 'zone' as a timezone name, which does not clarify how they relate to the tool's stated purpose. The url description is also contradictory, saying 'normalize or cite' rather than 'GitHub URL'.

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 one-line description states a clear intent—parse owner and repo from a GitHub URL—but the input schema contains nine unrelated parameters (city, feed, zone, query, etc.), making it ambiguous which fields are actually used and what the tool really does. The url parameter description ('HTTPS URL to normalize or cite') also conflicts with the GitHub-specific claim.

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 gives no guidance on when to use this tool instead of a sibling, no success criteria, and no hint about the expected input combination. With zero required parameters and a large, mixed schema, an agent cannot infer the intended usage.

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