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. It only mentions parsing owner/repo and does not state that the tool is a pure validation/parse with no side effects (though schema hints at 'discarded'), nor does it explain return values or how it handles the other parameters.

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 one short sentence, which is concise but severely under-specified. It omits critical information about parameter usage and tool scope, so the brevity works against clarity rather than for it.

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 nine parameters, no output schema, and no annotations, the description is grossly incomplete. An agent cannot determine which parameter to pass, what the tool returns, or how it behaves across different inputs. The mismatch between the description and schema makes it nearly unusable.

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 description coverage is 100%, so each parameter has a basic description (e.g., 'discarded after the shape check'). The tool description adds no extra meaning about which parameter is relevant for GitHub parsing or how parameters relate to each other, but the baseline is 3 given full schema coverage.

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 says 'Parse owner and repo from a GitHub URL,' which states a clear verb and resource. However, the input schema contains nine unrelated parameters (city, feed, json, path, zone, query, etc.) that are not mentioned in the description, making the tool's actual scope ambiguous. It does not distinguish itself from sibling shape-checkers 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 its siblings or on which parameter to supply for a GitHub URL. The description offers no conditions, exclusions, or alternative tools, leaving the agent to guess.

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