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

With no annotations, the description carries the full behavioral burden, but it only states the parse action. It does not disclose what happens for invalid or non-GitHub URLs, what the return shape is, or that all parameters except `url` are effectively ignored; the schema hints at discarding, but the tool description itself adds little behavioral context.

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 tight sentence with no filler, and the core action is front-loaded. It is efficient and easy to scan, though it sacrifices some contextual detail.

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?

Despite high schema coverage, there is no output schema or annotation, and the input schema contains nine unrelated optional parameters. The description does not explain the expected return value, failure behavior, or why the non-URL parameters exist, leaving an agent to infer key invocation details from the schema alone.

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%, and the schema itself marks every parameter except `url` as discarded, so the description does not need to repeat parameter details. The one-line description adds no extra parameter-level meaning, but the baseline is satisfied by the 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 states a specific verb ('Parse'), a concrete resource ('owner and repo'), and a clear source ('GitHub URL'). This distinguishes it from sibling shape tools such as figma-url-shape and jira-key-shape without needing to open their schemas.

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 implies use for GitHub URLs and owner/repo extraction, but it gives no explicit when-to-use or when-not-to-use guidance and names no alternatives among the many sibling tools. Usage context is clear but only implicit.

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