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

No annotations are present, so the description carries the behavioral burden. 'Parse' implies a non-mutating read-only operation, which is helpful, but the description does not disclose whether the URL is fetched, validated, or normalized, nor what happens with the other accepted inputs.

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. It states exactly what the tool does without redundant qualifiers.

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 core operation is simple and the description conveys it, but there is no output schema, no required parameters, and no explanation of the many optional inputs. An agent can guess that 'url' is the input, but the return shape and edge cases are left unspecified.

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?

The schema already describes every parameter, so the baseline is 3. The description adds key meaning beyond the schema by specifying that the 'url' should be a GitHub URL and that owner/repo are extracted, whereas the schema only says 'normalize or cite.' This clarifies the intended primary parameter.

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 names a specific verb ('Parse'), a specific resource ('GitHub URL'), and the extraction targets ('owner and repo'). It clearly distinguishes this from sibling shape tools like figma-url-shape or domain-shape.

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 choose this tool over alternatives, and it does not state any exclusions or prerequisites. An agent must infer from the tool name and siblings.

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