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

With no annotations available, the description carries the full burden. It discloses the core behavior (parsing a GitHub URL) but does not say that only the url parameter is used, that other parameters are discarded, or how invalid/non-GitHub URLs are handled.

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?

A single front-loaded sentence with no filler or repetition. 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?

Adequate for a simple parsing tool, but with no output schema the agent is left to infer the return shape (e.g., field names for owner/repo). It also would benefit from stating that only url matters and what happens on invalid input.

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 the baseline is 3, but the description adds meaning beyond the schema by identifying url as the GitHub URL to parse and by naming owner and repo as the expected output values. It does not add detail for the remaining parameters, but they are already described in the schema.

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?

States a specific verb ('Parse') and a specific resource ('owner and repo from a GitHub URL'), making the tool's job unambiguous. This also differentiates it from sibling shape tools like domain-shape or figma-url-shape, which target other URL forms.

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 use case is implied: use this when you have a GitHub URL and need its owner/repo. However, it does not explicitly state when not to use it or mention alternatives such as normalize-url or domain-shape, so the guidance is limited.

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