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 behavioral disclosure. The single word 'Parse' gives no information about side effects, error handling, validation strictness, or what happens with malformed URLs. The description is nearly silent on behavior beyond the basic action.

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 short (one sentence), which is concise but severely under-specified for a tool with nine parameters and no output schema. Important context such as required inputs, return value, and interaction with the 'shape check' pattern is omitted. This is under-specification, not effective conciseness.

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?

For a tool with nine parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain what the tool returns, which parameters are mandatory, whether it performs validation or normalization, or how it relates to the sibling shape tools. An agent cannot reliably invoke this tool correctly based on the provided information.

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?

Schema description coverage is 100%, so the schema documents each parameter, but the description adds no additional meaning and is misleading: it mentions only a GitHub URL while the schema includes nine parameters, many of which (city, feed, json, zone, etc.) are clearly unrelated to GitHub URL parsing. The description does not clarify which parameters are actually used or how they relate to the core purpose, so it fails to compensate for the schema's generic descriptions.

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?

States a specific action (parse owner and repo) on a specific resource (GitHub URL), which distinguishes it from sibling shape tools like domain-shape or figma-url-shape. However, it does not specify the output format or the exact set of relevant inputs, leaving some ambiguity about what 'parse' produces.

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 on when to use this tool versus the many sibling shape/check tools (e.g., domain-shape, figma-url-shape). The description implies it is for GitHub URLs but does not state exclusion criteria or when to prefer an alternative. An agent must infer the applicability.

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