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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Parse owner and repo', offering no information about return format, error handling, network access, or side effects. The schema hints that many parameters are 'discarded', but the description does not confirm which inputs are actually used, nor what the 'shape check' entails. This is a serious gap for a tool whose schema suggests more complex behavior.

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 sentence and front-loaded, which is efficient. However, it is so under-specified that conciseness crosses into incompleteness—critical information about the tool's actual input handling and output is missing. The short length is not a virtue when it fails to cover essential context.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description is woefully inadequate. It does not explain the purpose of the extra parameters, what the tool returns, or how to interpret the 'shape check' concept. An agent would be forced to guess or explore unnecessarily. The description is far from complete for the tool's apparent complexity.

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%, and the schema already documents each parameter individually. The description adds no meaning beyond the schema; it does not explain that only 'url' is relevant or how the other parameters interact. Since the schema already provides thorough descriptions, the baseline of 3 applies, but the description fails to leverage that baseline to clarify the core parameter semantics.

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 clear verb ('Parse'), resource ('owner and repo'), and source ('GitHub URL'), which distinguishes it from generic URL tools. However, the input schema exposes 9 unrelated parameters (e.g., city, zone, json) with hints like 'discarded after the shape check', creating ambiguity about whether the tool is actually a multi-purpose validator. The description does not clarify this mismatch, so the agent cannot be certain of the tool's true scope.

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 versus alternatives like normalize-url, browser-url-ok, or jira-key-shape. The description does not mention any conditions, exclusions, or criteria that would help an agent choose this tool over siblings. The only implicit hint is the word 'GitHub', but it is not elaborated.

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