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

No annotations are provided, so the description must carry the behavioral burden. It says the tool parses owner/repo, but it does not disclose whether the call is read-only, what gets returned for invalid URLs, or that many schema parameters are discarded. The 'discarded' hints live in the schema, not the description.

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 filler or repetition. It is front-loaded and immediately actionable. It is not penalized heavily for brevity, though it could include a bit more structure around inputs and outputs.

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 having nine parameters, no output schema, and no annotations, the description only covers one simple use case. It omits the return value shape, error behavior, and which inputs are relevant. This is inadequate for an agent to confidently select and invoke the tool for the full range of inputs the schema accepts.

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 coverage is 100%, so the baseline is 3. The description adds some meaning by implying that `url` is the key input for extracting owner and repo, but it never explicitly names the parameter nor explains the role of the other eight parameters. The schema descriptions already cover each parameter, so the description's added value is limited.

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 action ('Parse'), the resource ('GitHub URL'), and the expected result ('owner and repo'). It differentiates from sibling URL tools like normalize-url or fetch-status by naming GitHub repo parsing specifically. It loses a point because it doesn't mention the tool's broader shape-checking behavior implied by the schema.

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 about when to use this tool versus alternatives such as normalize-url, domain-shape, or figma-url-shape. The description implies a use case but provides no exclusions, no prerequisite context, and no comparison to other URL-related tools.

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