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

The verb 'parse' suggests a read-only operation, and some schema descriptions mention discarded values or no disk access, implying no persistent side effects. However, the tool description itself does not explicitly state whether network access, authentication, or any mutation is involved.

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 or redundant wording. It directly states the action and target.

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 description gives the core purpose but omits the return format, behavior for invalid URLs, and which optional parameter to provide. Given the broad and ambiguous schema, this leaves important operational context missing.

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 input schema is largely misaligned with the stated purpose: the url parameter is described as 'normalize or cite' rather than as a GitHub URL, and eight unrelated optional parameters are present. The tool description provides no guidance on which parameter should actually be used to parse a GitHub repository.

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 action and resource: parse owner and repo from a GitHub URL. This distinguishes it from sibling shape tools focused on domains, Figma URLs, or Jira keys.

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 explicit guidance is given for when to use this tool versus alternatives such as normalize-url, domain-shape, or figma-url-shape. The intended use is only implicit: when a GitHub repo owner and name need to be extracted.

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