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

For a parser, the core behavior is transparent: it parses owner and repo and does not imply mutation. However, with no annotations and no output schema, the description does not disclose how invalid or non-GitHub URLs are handled, and it does not explain why the schema includes many unrelated fields like city, json, and path.

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. Every word contributes to the core meaning, making it easy to scan and parse.

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?

There is no output schema and the description does not describe what the parsed result looks like or how errors are surfaced for non-GitHub URLs. The presence of many seemingly unrelated parameters creates ambiguity that the description does not resolve, so the agent cannot fully anticipate the tool's behavior.

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?

All parameters have schema descriptions, so the description does not need to cover them. The relevant 'url' parameter is described as 'HTTPS URL to normalize or cite', which is somewhat helpful but does not clarify that it should be a GitHub repository URL.

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') and resource ('owner and repo from a GitHub URL'), making the tool's core function unmistakable. It also distinguishes this tool from sibling shape tools like jira-key-shape or domain-shape by explicitly scoping it to GitHub URLs.

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 this tool is for extracting owner and repo from GitHub URLs, but it never explicitly says when to use it instead of alternatives such as domain-shape or figma-url-shape. There are no exclusions or alternative conditions stated.

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