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

With no annotations, the description must disclose behavioral traits. It only says 'Parse', which implies a read-only operation, but it doesn't mention that many parameters are discarded, that it only uses the url parameter, or what the output format is. The schema hints at discarding behavior, but the description adds no transparency beyond a simple parse.

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, short sentence with no waste. It front-loads the core action. However, given the complexity of the schema (9 params), the brevity leaves critical information unstated, so it's not perfectly concise in the sense of being complete yet compact.

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 tool has 9 parameters, but the description only covers the URL parsing aspect. It doesn't explain why the other parameters exist, what the tool returns, or any prerequisites. With no output schema, the agent has no idea what the response looks like. This is inadequate for a tool with this parameter count.

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 schema already documents all 9 parameters. The description adds no extra meaning to any parameter; it only refers to 'GitHub URL', which likely maps to the 'url' parameter. Since coverage is high, the baseline is 3, and the description fails to add value beyond that.

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 clearly states a specific verb ('Parse') and resource ('owner and repo from a GitHub URL'). It distinguishes from sibling shape tools like figma-url-shape and jira-key-shape by specifying GitHub. However, it doesn't mention the other 8 parameters, so the overall purpose is partially obscured by the schema's breadth.

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?

No guidance on when to use this tool versus alternatives. It implies use when you have a GitHub URL and need owner/repo, but doesn't explicitly state when not to use it or recommend sibling tools for other URL types. No exclusions or conditions are given.

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