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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Parse owner and repo from a GitHub URL,' with no mention of how invalid URLs are handled, what the output format is, or that other schema parameters are discarded. This is a significant gap for a tool with such a sparse 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, efficient sentence with no wasted words. It is appropriately concise, though it sacrifices completeness for brevity. The front-loading is acceptable for a simple action, but the lack of supporting detail prevents a 5.

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, no output schema, and no annotations, yet the description is extremely minimal. It fails to specify which parameters are relevant, what the tool returns, error behavior, or any edge cases. This is entirely inadequate for an agent to invoke the tool correctly without additional external knowledge.

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 each parameter already has a description. The tool description adds no new meaning about parameters—it does not clarify that only 'url' is used, nor does it elaborate on the discarded parameters. Baseline 3 is appropriate given the high schema coverage, but the description provides no added value beyond 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?

The description states a clear, specific verb ('Parse') and resource ('owner and repo from a GitHub URL'), which distinguishes it from sibling shape tools like domain-shape or figma-url-shape. However, it does not explicitly mention that the tool only uses the 'url' parameter, leaving some ambiguity about its scope given the schema's many unrelated parameters.

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 is provided on when to use this tool versus the sibling shape-checking tools. The description does not mention alternatives, exclusions, or conditions for selection, leaving the agent to infer context from the name alone.

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