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

With no annotations present, the description carries full responsibility for behavioral disclosure, but it only says 'parse'. It does not state that the operation is local and non-network, what happens for non-GitHub URLs, how errors are surfaced, or that many of the accepted parameters are ignored/discarded; the schema's per-parameter notes partly cover this, but the description itself does not.

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?

One clean sentence with no filler, front-loading the operative verb and resource. It is appropriately terse for the core purpose, though the lack of any mention of the broader shape-check behavior makes it minimally concise rather than exemplary.

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?

For a simple parse tool this is nearly sufficient: the agent can infer that it should supply a GitHub URL in `url` and expect owner/repo. But there is no output schema and no annotation safety net, and the large list of unrelated-looking optional parameters is unexplained by the description, so an agent cannot fully predict return format or failure 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?

Schema description coverage is 100%, so the baseline is 3; the description does add the useful hint that the `url` parameter should be a GitHub URL and that owner/repo are the extracted result. It does not explain why the other optional parameters exist or whether they affect the result, but the schema already documents each one.

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 names a specific action ('parse'), a specific resource ('a GitHub URL'), and a concrete result ('owner and repo'), making the tool's core function immediately clear and distinguishing it from sibling shape tools like `figma-url-shape` or `jira-key-shape`. It does not explicitly frame the operation as a local shape check, but the core purpose is unambiguous.

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 gives a clear implied use case: whenever an agent has a GitHub URL and needs owner/repo extraction. However, it offers no explicit exclusions, no mention of when another sibling tool should be used instead, and no statement about whether this should precede or substitute for URL validation or fetching.

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