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

No annotations are provided, and the description does not disclose behavioral traits such as return format, error handling, or that it discards unused parameters. It only restates the core action without adding any transparency beyond the tool name.

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 extremely concise at one sentence, but it is under-specified for a tool with 9 parameters. It lacks essential context and reads more like an under-specification than a well-structured concise description. While it is not verbose, it fails to earn its place by omitting crucial 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?

With 9 parameters, no annotations, and no output schema, a single sentence is completely inadequate. The agent has no information about what the tool returns, how it handles invalid inputs, or which parameters are relevant. This fails the completeness bar for a tool of this complexity.

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?

The description does not mention any parameters, but the input schema covers all 9 parameters with detailed descriptions (100% coverage). Per the rubric, baseline is 3 when schema coverage is high, and the description adds no additional semantic value beyond what the schema already provides.

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') and resource ('GitHub URL') and the expected output ('owner and repo'). It clearly distinguishes from siblings like figma-url-shape and jira-key-shape by scoping to GitHub.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention conditions for use, prerequisites, or exclusions. The implied context from the name and description is weak and relies on the agent inferring the appropriate use case.

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