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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without mentioning whether it is read-only, performs network calls, validates the URL, or what happens on invalid input. This is a significant gap for a tool that likely has side effects or validation logic.

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 sentence, making it concise, but it is under-specified. It does not earn its place because it omits critical information about the tool's behavior and parameters. Conciseness is not a substitute for completeness.

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?

Given the tool has 9 parameters, no annotations, and no output schema, the description is grossly incomplete. It does not explain the purpose of the other parameters, the return value, or the conditions under which the tool should be called. An agent cannot reliably invoke this tool correctly based on the description alone.

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?

The schema has 9 parameters with descriptions, but the description adds no meaning beyond the schema. The schema descriptions are generic and some are unrelated to GitHub URL parsing (e.g., city, feed, zone). The description does not clarify which parameters are relevant, so an agent cannot determine that 'url' is the primary input. The high schema coverage does not compensate because the schema itself is 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 states a specific verb and resource: 'Parse owner and repo from a GitHub URL.' This clearly differentiates it from siblings like domain-shape or figma-url-shape. However, it is terse and does not elaborate on the scope or edge cases, so it loses one point for lack of detail.

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. It does not mention that it is specifically for GitHub URLs or that other URL shape tools should be used for other domains. The agent is left to infer the appropriate context.

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