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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The one-liner only says it 'parses' but gives no information about return values, side effects, how it handles the various parameters, or what happens with non-GitHub inputs. The agent has no idea what to expect.

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 concise sentence, but it is severely under-specified for a tool with 9 parameters. It is not efficient conciseness; it is under-specification that omits essential context about the tool's scope and behavior.

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's complexity (9 parameters, no output schema, no annotations), the description is wholly inadequate. It does not explain the overall purpose, how to use it, or what the agent can expect, leaving the agent without enough information to call 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?

Schema coverage is 100%, so the baseline is 3, but the description adds no meaning beyond the schema and actively misleads by implying the 'url' parameter is the sole focus. It fails to explain that the tool likely processes only one of the parameters at a time or that it is polymorphic, so it does not help the agent understand how to pass parameters correctly.

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 and resource ('Parse owner and repo from a GitHub URL'), but the input schema includes fields for city, JSON, timezone, search, etc., indicating the tool is actually a generic parser/validator for many input types. This is misleading and does not represent the tool's real scope, nor does it distinguish it from siblings like domain-shape or figma-url-shape.

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 the many sibling tools with similar 'shape' names. The single sentence implies GitHub URL parsing, but the schema suggests a broad multi-purpose tool, so the agent receives no direction about which context calls for this tool or when to choose an alternative.

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