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

No annotations are present, and the description only mentions parsing without disclosing side effects, error behavior, or whether the operation is read-only. The schema contains many unrelated fields (city, feed, zone) that contradict the stated purpose, further muddying behavioral expectations.

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 that directly conveys the core function without unnecessary verbiage. It is well-structured and easy to scan.

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 description lacks essential context such as input format expectations, return value structure, error handling, or any example usage. With no output schema and a confusing parameter set, an agent cannot reliably know how to invoke this tool correctly or interpret its results.

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?

While the schema has 100% description coverage, the parameter descriptions are generic and largely irrelevant to parsing a GitHub URL. For example, 'city' is described as a weather hint and 'zone' as a timezone name, yet the tool is supposed to parse owner and repo. The 'url' parameter is the only one that aligns with the purpose, but the other 8 parameters are misleading.

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 tool's purpose with a specific verb ('Parse') and resource ('GitHub URL'), and it distinguishes from sibling tools like figma-url-shape or domain-shape. The intent is unambiguous.

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 alternatives such as normalize-url or figma-url-shape. The description does not mention conditions, limitations, or when not to use it.

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