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 owner and repo,' but does not explain what happens to other inputs (many are marked 'discarded' in the schema), what the output format is, or whether validation is performed. The description is misleading in its narrowness, as the schema implies a more general shape-checking capability.

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 with no waste. However, given the tool has nine parameters and a complex schema, the brevity leaves critical information out. It is efficient but under-specified, so it neither earns a high score for completeness nor a low score for verbosity.

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 is complex (9 parameters, no output schema) and the description covers only a fraction of its behavior. It does not explain the role of the other parameters, the expected output, or any error conditions. An agent cannot reliably determine how to invoke the tool for anything other than a simple GitHub URL parse.

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 adds no parameter-level meaning; it does not connect any of the nine parameters to the parse action. However, it does not actively mislead, and the schema already provides descriptions for each parameter, albeit generic ones that do not align with the stated purpose.

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 action ('Parse owner and repo') and resource ('GitHub URL'), which is clear. However, it fails to mention the other eight parameters in the schema, making the tool's actual scope ambiguous. It also does not differentiate it from sibling shape tools like 'domain-shape' or '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 description gives no guidance on when to use this tool versus alternatives. It does not mention any conditions or contexts where parsing a GitHub URL is preferred, nor does it indicate exclusions (e.g., other URL shapes). An agent has no basis for choosing this tool over others.

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