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

No annotations are provided, so the description carries the full burden, but it fails to explain behavior. Param descriptions state that values are 'discarded after the shape check,' 'discarded after the length check,' or that there is 'no disk access,' yet the description claims the tool parses owner and repo from a GitHub URL — the relationship between discarding params and parsing is unexplained. It is unclear whether the tool has side effects, what it returns, or how it handles malformed input.

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 itself is concise — a single sentence — but the overall structure is bloated with nine unrelated parameters that lack any coherent organization or grouping. The mismatch between the minimal description and the sprawling schema makes the tool definition feel cluttered and incoherent, diminishing the value of the brevity.

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 nine parameters, zero required fields, no output schema, and no annotations, the description leaves critical gaps: it never states what the output looks like (an object? strings?), how errors surface for non-GitHub URLs, or which parameter (if any) actually holds the URL. The disconnected parameter descriptions raise more questions than they answer, making the tool insufficiently specified for reliable agent use.

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 coverage is 100%, the parameter descriptions are copy-paste artifacts from unrelated tools: 'city' references a weather hint, 'zone' an IANA timezone, 'json' a validation check, 'query' a length check, and 'feed' an RSS URL. None of these map meaningfully to parsing a GitHub URL's owner and repo; even the 'url' parameter's description mentions 'normalize or cite,' which conflicts with the parsing purpose. The descriptions actively mislead rather than clarify parameter roles.

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), resource (owner and repo), and scope (from a GitHub URL), which is clear in isolation. However, the input schema contains nine unrelated parameters (city, zone, json, query, path, feed, host) whose descriptions reference weather hints, timezones, JSON validation, and length checks, none of which align with GitHub repo parsing. This mismatch between description and schema undermines purpose clarity for an agent trying to understand what the tool actually does.

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 like normalize-url, domain-shape, figma-url-shape, or jira-key-shape. There is no mention of prerequisites (e.g., URL format expected), fallback behavior for invalid URLs, or when this tool is preferred over sibling tools. An agent receives zero directional support for tool selection.

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