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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'Parse owner and repo' and does not explain what happens for invalid URLs, whether the input is validated, what output is returned, or how unrelated schema fields like city, feed, host, json, and path behave.

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 wasted words. It immediately communicates the core action and target resource.

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 seven schema parameters, no annotations, and no output schema, this one-sentence description is insufficient. It lacks return format, validation behavior, parameter selection guidance, and error semantics, leaving significant gaps for an agent deciding how to invoke it correctly.

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 schema provides descriptions for all seven parameters, so the baseline is 3 despite no parameter details in the tool description. However, the description does not clarify that 'url' is the key parameter for this tool, and the schema descriptions like 'normalize or cite' do not fully align with the stated purpose of parsing owner and repo.

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'), which clearly distinguishes this from generic URL tools like normalize-url. However, it does not mention the validation/checking behavior implied by the tool name 'shape', so it is clear but slightly incomplete.

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 related siblings such as domain-shape, figma-url-shape, or normalize-url. The description implies it is for GitHub URLs, but it never explicitly says when to prefer this tool or what alternatives exist.

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