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

No annotations are present, and the description does not disclose error behavior, handling of invalid or non-GitHub URLs, ignored parameters, or the exact shape of the returned owner/repo result. A read-only operation is implied but not explicitly stated.

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 that front-loads the action and target with no filler or redundancy.

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?

With no output schema and a bloated, conflicting input schema containing unrelated parameters, the description is insufficient for an agent to confidently call the tool. It does not explain the expected return format or how to handle the irrelevant fields.

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?

Despite 100% schema description coverage, the parameter descriptions are mismatched and largely irrelevant. Only 'url' is plausibly related to the stated purpose, while city, feed, zone, query, and others appear copied from unrelated sibling tools. The description does not clarify which parameters are actually used.

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 verb and resource: 'Parse owner and repo from a GitHub URL.' This distinguishes the tool from sibling URL/shape tools and leaves little ambiguity about its primary function.

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 about when to use this tool versus alternatives like normalize-url, figma-url-shape, or browser-url-ok. The intended use case must be inferred from the wording.

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