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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It says 'parse' but does not state that other parameters (like 'city', 'feed', 'json') are ignored or discarded, nor does it indicate what happens on failure (e.g., returns null or throws). The schema descriptions mention 'discarded' for some params, but the tool description itself provides no behavioral context about the operation's side effects or error handling.

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, succinct sentence with no extraneous words. It front-loads the core action clearly. While it lacks depth, it is appropriately concise for a tool that appears to perform a simple extraction, and there is no filler or redundant phrasing.

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?

Given the tool has 9 parameters and no output schema, the description is incomplete. It does not specify which parameter is used, what the return value looks like (owner and repo in what format), or how the tool behaves with invalid URLs. An agent calling this tool would need to infer that 'url' is the relevant input and would have no information about the result structure, making the description inadequate for effective invocation.

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 schema description coverage is 100%, so the baseline for this dimension is 3. The description does not add meaning beyond the schema—it does not highlight that 'url' is the primary parameter or clarify the role of the other eight parameters. Since the schema already describes each parameter individually, the description fails to compensate for the potential confusion caused by the many unrelated parameters in this small tool.

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 specific resource ('GitHub URL'), making the core purpose clear. However, it does not differentiate itself from sibling shape-checking tools like 'domain-shape' or 'jira-key-shape' by mentioning that it validates or extracts a particular shape. The action is unambiguous, but the scope is narrow enough that it could be confused with a general URL parser if not for the GitHub keyword.

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 use this tool versus alternatives. The description does not mention that it is specifically for GitHub URLs, nor does it exclude non-GitHub URLs or explain that only the 'url' parameter is relevant. Without any context about prerequisites, exclusions, or alternative tools, an agent cannot determine when this is the appropriate choice among the many sibling shape checkers.

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