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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Parse', which hints at a local, non-mutating operation, but it does not state what happens for malformed URLs, whether the URL is fetched or validated, or what errors occur. The 'discarded after the shape check' notes in the schema are not reflected in the description.

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. It presents the action, object, and result before any possible elaboration, which is optimal for the limited content it covers.

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 tool with nine optional parameters, no required parameters, and no output schema, one sentence is not enough. The description does not identify which parameter to populate, what is ignored, what the return shape is, or how invalid input is handled. The schema's generic parameter descriptions do not compensate.

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. The description adds the critical meaning that the subject is a GitHub repo URL and that owner/repo are extracted, but it never names the 'url' parameter or explains why the other eight optional parameters exist, leaving a large mapping gap.

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 gives a specific verb ('Parse'), a specific resource ('GitHub URL'), and the expected result ('owner and repo'), which makes the core purpose unambiguous. The GitHub-specific wording separates it from sibling shape tools like domain-shape, jira-key-shape, and 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?

The wording implies the tool is for extracting repository components from a GitHub URL, but it gives no explicit when-to-use guidance and names no alternatives. With 27 sibling tools, an agent must infer that this tool is preferred over normalize-url or browser-url-ok, rather than being told.

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