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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention what the tool returns, whether it validates or extracts, or how it handles the other schema parameters. The schema indicates that many parameters are discarded, but the description does not clarify that only the url is relevant.

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, which is concise, but it lacks any detail about behavior or parameters. It is appropriately short but fails to provide essential context, so it is not well-structured for an agent to understand the tool's scope.

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 incomplete. It does not explain what the tool returns, how to use the url parameter, or why there are many unrelated parameters. An agent would be confused about which parameters to provide.

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 covers all 9 parameters with descriptions (100% coverage), and the description adds that the url should be a GitHub URL, which is helpful. However, it does not clarify that the other parameters are irrelevant to this tool's purpose, so parameter semantics are only partially clarified.

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 tool parses owner and repo from a GitHub URL, which is a specific verb-resource combination and distinguishes it from sibling tools like domain-shape (domain parsing) and figma-url-shape (Figma URL parsing). The purpose is unambiguous.

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 or browser-url-ok. The description only states what it does, not when to choose it, nor any exclusions or prerequisites.

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