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

With no annotations, the description carries the full burden. 'Parse' implies a read-only operation, but the description does not disclose behavior on invalid or non-GitHub URLs, whether it validates URL structure, what it returns, or that many schema parameters are discarded after a shape check.

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, front-loaded sentence with no filler. It is efficient, though it omits enough contextual guidance that it borders on under-specified.

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?

The tool has no annotations, no output schema, and a large input schema with unrelated-looking parameters such as city, feed, json, path, and query. A one-line parse description is insufficient for an agent to know which parameter to pass, what output to expect, or how to handle edge cases.

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 high, so the baseline is 3. The description adds specific meaning to 'url' (GitHub owner/repo extraction) but conflicts slightly with the schema's generic 'HTTPS URL to normalize or cite' and does not clarify the relevance of the remaining 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 states a specific action ('Parse') and a specific resource ('owner and repo from a GitHub URL'), making the core purpose clear. It does not, however, explicitly distinguish this from sibling shape tools or explain what a successful parse returns.

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 given about when to prefer this tool over siblings like figma-url-shape, jira-key-shape, or normalize-url, nor any exclusions such as handling non-GitHub URLs. An agent must infer context.

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