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

No annotations are provided, so the description carries the full burden. It only says 'Parse', implying a read operation, but doesn't disclose that most parameters are discarded (though the schema descriptions do), doesn't describe error behavior or output format, and doesn't clarify side effects. For a tool with 9 parameters, this is a significant gap.

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 concise sentence, which is not verbose. However, given the tool's complexity (9 parameters) and the existence of many sibling tools, the description is under-specified. It does front-load the core purpose but lacks detail needed for correct usage.

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 no output schema and a 9-parameter input schema with no required fields. The description doesn't explain what the tool returns (owner/repo presumably), how the parameters are used, or what happens with invalid input. Given the complexity, this is insufficient for an agent to call the tool correctly.

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 each parameter has a description, but the tool description adds no meaning beyond the schema. It doesn't explain how the parameters relate to parsing owner/repo or which are required. The baseline for full schema coverage is 3, and the description neither enhances nor contradicts the schema.

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?

States a specific verb ('Parse') and resource ('owner and repo from a GitHub URL'), which distinguishes it from sibling shape tools like domain-shape and figma-url-shape. However, it doesn't clarify the purpose of the many additional schema parameters, leaving ambiguity about what the tool actually does with them.

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 the many sibling shape tools. It doesn't mention prerequisites, conditions, or alternative tools for non-GitHub URLs. The description only states the action without context for selection.

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