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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the parsing action and omits critical traits: whether the operation is read-only, what it returns, or how it handles malformed or non-GitHub URLs. The schema's many parameters marked as 'discarded' imply the tool accepts and ignores extras, but the description doesn't state this, leaving agent expectations unclear.

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 sentence with no filler, front-loading the action and resource. It is efficient and free of redundancy. However, its brevity borders on under-specification, though conciseness itself is not the problem—the lack of context is. The structure is appropriate for the little it says.

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?

Given the tool has 9 parameters, no output schema, and no annotations, a one-sentence description is grossly inadequate. An agent cannot determine which parameters to use, what the tool returns, or how it behaves under different inputs. The description fails to provide the minimum context needed for correct invocation, especially since most parameters seem irrelevant to the stated purpose.

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%, but the tool description adds no meaning beyond that. Only 'url' seems relevant to the stated purpose, yet the schema exposes nine parameters with descriptions suggesting they belong to unrelated checks (city, feed, json, etc.). The description fails to indicate that most parameters are ignored, which could mislead an agent into passing irrelevant arguments.

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 verb 'Parse' and the resource 'owner and repo from a GitHub URL', making the primary purpose unambiguous. It also differentiates from sibling shape tools by specifying GitHub-specific extraction. However, it does not describe the output format or error handling, so it's clear but not fully comprehensive.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools like figma-url-shape, jira-key-shape, and domain-shape exist for other URL types, but the description never mentions them or any selection criteria. An agent has no basis to choose this tool over similar shape-checking tools.

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