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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'parse' and doesn't explain that the tool likely validates or shape-checks inputs, nor does it mention that many schema parameters are discarded after the check. The mismatch between the description's extraction focus and the schema's 'discarded after the shape check' hints is a significant transparency gap.

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 concise sentence with no wasted words. However, it is so brief that it omits essential context about the tool's broader behavior, which detracts from its effectiveness despite its efficiency.

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, no output schema, and no annotations, the description is severely under-specified. It doesn't explain the return value, the validation behavior, or how the non-URL parameters are handled. An agent cannot correctly invoke this tool for the full set of inputs described in the schema.

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%, so each parameter is already documented in the schema. The description adds marginal value by implying the 'url' parameter is a GitHub URL, but it doesn't clarify the role of the other eight parameters. Since the schema does the heavy lifting, a baseline of 3 is appropriate.

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) on a specific resource (owner and repo from a GitHub URL), which distinguishes it from sibling shape-checking tools like figma-url-shape or jira-key-shape. However, it doesn't account for the broader set of parameters in the schema, which suggest the tool handles more than just GitHub URLs, creating ambiguity about its 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. The description doesn't mention conditions like 'use this when you have a GitHub URL' or direct users to siblings for other URL types. This leaves the agent to infer usage context, which is insufficient.

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