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 only states the core parsing action and does not mention that many parameters are discarded, that the operation is read-only, or what the output looks like. The schema hints at discarding, but the description itself is silent.

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, efficient sentence that front-loads the core purpose without any filler. Every word earns its place.

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 9 parameters, no output schema, and no annotations, a one-sentence description is insufficient. It does not explain how parameters like city, feed, or json relate to the tool, nor does it describe the return format or error behavior. An agent cannot confidently call this tool correctly without additional inference.

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 description coverage is 100%, so the baseline is 3. The tool description adds no parameter-level detail beyond the schema, which already documents each parameter. However, the description does not clarify which parameters are actually relevant to the URL parsing task, leaving potential confusion about the many unrelated parameters.

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 verb 'parse' and the resource 'GitHub URL', specifying it extracts 'owner and repo'. This distinguishes it from sibling URL-shape tools like domain-shape, figma-url-shape, and jira-key-shape, which target other domains.

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 gives no guidance on when to use this tool versus alternatives such as normalize-url or browser-url-ok. It does not mention exclusions or conditions for selection; usage is only implied by the tool's name and the phrase 'GitHub URL'.

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