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

With no annotations and no behavioral details, the description leaves side effects, return values, error behavior, and read-only guarantees completely unspecified. The phrase 'discarded after the shape check' in parameter descriptions hints at some internal behavior but is too vague to be informative.

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 wasted words and the main intent is front-loaded. However, it lacks any supporting structure or detail about parameters, output, or usage context.

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 nine parameters, none required, and no output schema, yet the description does not explain the role of irrelevant-looking inputs like 'city', 'zone', or 'query'. This leaves the context highly ambiguous and incomplete for an agent deciding whether and how to invoke it.

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 the schema has descriptions for all nine parameters, most are unrelated to GitHub repo parsing (e.g., 'city', 'feed', 'zone', 'json') and appear copied from other tools. There is no clear explanation of how 'url' is used or why the other parameters exist, so the schema actively undermines rather than clarifies parameter meaning.

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 clearly states the action ('Parse') and the target ('GitHub URL'), as well as the intended result ('owner and repo'). It is reasonably distinguishable from sibling URL-related tools, though it does not specify the output format or which parameter holds the URL.

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 explicit guidance on when to use this tool versus alternatives like normalize-url, domain-shape, or figma-url-shape. The mention of 'GitHub URL' implies the use case, but there is no direct comparison or exclusions.

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