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

There are no annotations, so the description carries the full burden of behavioral disclosure. It reveals parse intent but does not describe the return structure, invalid-URL handling, normalization behavior, or whether this is purely a validation check.

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 core action and resource. Every word earns its place, even though the brevity contributes to incompleteness.

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?

With 9 optional parameters, 0 required parameters, no annotations, and no output schema, one sentence is not enough. The agent does not know which parameter to pass, what the return value contains, or how invalid inputs are handled.

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 does add useful GitHub-specific meaning to the otherwise generic `url` parameter, but it never names `url` or clarifies why eight other optional parameters exist. The schema's 'normalize or cite' wording for `url` also creates minor semantic friction.

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 states a specific verb ('Parse'), a specific resource ('a GitHub URL'), and the expected outcome ('owner and repo'). It distinguishes this tool from sibling shape tools like figma-url-shape and jira-key-shape through the explicit GitHub focus.

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 implies the tool should be used for GitHub URLs, but it does not explicitly say when not to use it or which sibling to use for non-GitHub URLs. Given the many URL and shape-related siblings, the routing is left mostly to inference.

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