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

With no annotations, the description carries the full burden, yet it only states the parse action. It does not disclose how malformed or non-GitHub URLs are handled, whether any other parameters are ignored, or what the response looks like.

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?

One sentence, front-loaded with the verb and resource, with no filler or repeated schema information. 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?

The description is enough for a simple call: provide a GitHub URL and expect owner and repo. However, with nine optional parameters, no required fields, no output schema, and no annotations, it leaves return shape, invalid-input behavior, and routing details unstated.

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 description adds a little semantics by clarifying that the URL is a GitHub URL and that owner/repo are extracted, but it does not resolve which of the eight other optional parameters are relevant.

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 concrete verb ('parse'), a specific resource ('GitHub URL'), and an explicit outcome ('owner and repo'). This distinguishes it from sibling tools like figma-url-shape or jira-key-shape without requiring the schema to be opened.

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 phrase 'from a GitHub URL' implies when to use the tool, but the description gives no explicit routing, no exclusions, and no mention of alternatives such as normalize-url or domain-shape for non-GitHub URLs. Usage is inferable, not stated.

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