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

With no annotations, the description carries the full behavioral disclosure burden. It only says 'Parse' and does not explain what happens with invalid GitHub URLs, whether it validates the URL, what it returns beyond owner/repo, or that the many other input parameters are discarded.

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 one short, front-loaded sentence with no filler. It delivers the core purpose immediately and every word contributes meaning.

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?

This is a 9-parameter tool with no output schema and no annotations, yet the description only covers the basic parse intent. It omits return format, required parameter behavior, invalid-input handling, and the fact that most parameters appear to be discarded.

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 schema already documents all parameters. The description adds context that the URL should be a GitHub URL and that the meaningful extracted result is owner and repo, but it does not clarify which parameter is required or how the unrelated parameters interact.

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'), a specific resource ('owner and repo'), and the input source ('GitHub URL'). This clearly distinguishes it from sibling shape tools like figma-url-shape or jira-key-shape by naming the exact output and input domain.

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 when to use the tool: when you need to extract owner and repo from a GitHub URL. However, it does not explicitly mention alternatives, exclusions, or what to do when the URL is not a GitHub URL.

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