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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does not explain what the tool returns, how it handles invalid or non-GitHub URLs, or that the schema contains many unrelated parameters that are ignored. This is a significant transparency 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 single sentence is short and contains no filler, but it is under-specified rather than appropriately concise. It lacks structure, early indicators of parameter usage, and would not be considered a well-rounded feature description.

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 no output schema annotations, the description must explain return values and input expectations; it does neither. An agent cannot determine which of the nine seemingly irrelevant fields to supply, how the owner/repo are returned, or what happens for malformed input.

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?

Although schema description coverage is 100%, the 9 parameters are generic and some clearly belong to sibling tools (e.g., 'city', 'query', 'zone'). The description does not specify which parameters are relevant for a GitHub URL, adding confusion rather than compensation.

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 specific resource ('GitHub URL'), and the exact output concept ('owner and repo'). This clearly distinguishes it from sibling shape tools like 'jira-key-shape' or 'figma-url-shape' without requiring schema inspection.

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 such as 'normalize-url' or other shape tools. It does not mention context, prerequisites, or any exclusions, leaving the agent to infer usage 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.