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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says it parses owner and repo, but does not mention error handling, return format, side effects, or the fact that other parameters are discarded. The schema hints at validation behaviors (e.g., 'discarded after the shape check'), but the description omits these entirely. This is a serious gap for a tool with no annotations.

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 concise at one sentence, but it is under-specified relative to the complexity of the schema. While it front-loads the primary purpose, it omits any mention of the additional parameters or their purpose, making the structure appear incomplete rather than efficiently minimal. The sentence earns its place but does not adequately structure the tool's behavior.

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 nine parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the return value, how to handle errors, or how the non-url parameters interact with the parsing logic. An agent would be unable to confidently invoke this tool for anything beyond a simple GitHub URL, and the presence of unrelated parameters would likely lead to misuse.

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 each parameter has a description, but the tool description does not add any extra meaning. It does not clarify how the url parameter is used or why the other eight parameters exist. The description's mention of only 'URL' fails to explain the role of parameters like 'ref', 'city', or 'json', leaving the agent without a coherent model of how to invoke the tool correctly.

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 ('parse') and resource ('owner and repo from a GitHub URL'), which distinguishes it from siblings like 'normalize-url' or 'figma-url-shape'. However, the schema exposes nine unrelated parameters (city, feed, json, etc.) that the description does not account for, creating ambiguity about the tool's true scope. The core purpose is clear, but the schema undermines it slightly.

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 only states what it does, without mentioning when it is appropriate or when another tool (e.g., 'normalize-url' for generic URLs) should be preferred. An agent would have to infer usage from the name and description alone.

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