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

No annotations are provided, so the description must disclose behavior. It only says 'parse owner and repo' without stating what happens on invalid input, whether the tool validates the URL, what the return format is, or why the schema includes nine unrelated optional parameters (e.g., city, feed, json). The description does not address these behavioral aspects, leaving significant gaps for an agent.

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, focused sentence with no filler. It is front-loaded with the action and resource, making it easy to scan. Every word contributes to the purpose.

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?

Despite the tool appearing simple, the context is incomplete. With nine optional parameters and no required ones, the description does not specify which parameters are needed or how they interact. There is no output schema, and the description fails to explain what the tool returns (e.g., owner and repo as separate fields, a combined string, etc.). The presence of unrelated parameters like 'city' and 'feed' is unexplained, leaving an agent uncertain about the actual expected input and behavior.

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%, but the schema does not mention owner or repo. The description adds the concept of extracting owner and repo, but it does not clarify which parameter (likely 'url') is the primary input or how the other parameters relate. This creates ambiguity; for example, the schema describes 'url' as 'HTTPS URL to normalize or cite', not specifically for GitHub parsing. The description provides some added meaning but does not fully reconcile the mismatch.

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 the tool's function: parse owner and repo from a GitHub URL. It uses a specific verb ('parse') and resource ('owner and repo'), and the mention of 'GitHub URL' distinguishes it from sibling tools like figma-url-shape and jira-key-shape. Though it doesn't explicitly name alternatives, the purpose is unambiguous.

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 implies usage when a GitHub URL is provided, but it does not explicitly state when to use it versus alternatives, nor does it mention any exclusions or prerequisites. It is minimal guidance, relying on the tool name and context. There is no explicit 'use this when...' or 'do not use when...'.

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