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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Parse', but does not explain whether the tool validates the URL, what happens on invalid input, whether it performs network access, or what the result looks like. The input schema's 'discarded after the shape check' phrasing hints at side-effect-free behavior, but the description itself does not disclose this.

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, which is highly concise. It is slightly too sparse given the nine-parameter schema and missing behavioral details, so it earns a 4 rather than a 5.

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?

The description is not complete enough for confident invocation: the tool has nine optional parameters, no required parameters, no output schema, and no annotations. The description only explains one conceptual operation and never tells the agent which parameter to populate, what the other parameters do in this context, or what return value to expect.

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 schema already documents all nine parameters. The description adds GitHub-specific context for the `url` parameter, but it does not clarify how the other eight unrelated parameters should be handled, and the schema's own `url` description ('HTTPS URL to normalize or cite') conflicts somewhat with the 'parse owner and repo' framing.

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 action ('Parse') and object ('owner and repo from a GitHub URL'), making the tool's core purpose immediately understandable. It is naturally distinct from sibling shape tools like jira-key-shape or figma-url-shape, though it does not explicitly name an alternative.

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 intended use is implied: use this tool when you need to extract owner and repo from a GitHub URL. However, it provides no explicit guidance about when not to use it or how it compares to related tools such as normalize-url or domain-shape.

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