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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that only the 'url' parameter is relevant, that other parameters are discarded, or what the tool returns. There is no indication of validation, side effects, or error behavior.

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 fluff or redundancy. It is appropriately short, though it sacrifices necessary detail for 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?

For a tool with nine parameters and no output schema, the description is severely incomplete. It does not explain the expected input format, return value, or behavior when non-URL parameters are supplied. An agent would not be able to call this tool correctly without additional 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?

Although the schema provides descriptions for all nine parameters, the tool description does not connect its stated purpose to any specific parameter. It does not clarify that 'url' is the relevant input, leaving the agent to guess which of the nine fields to populate.

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: parse owner and repo from a GitHub URL. This distinguishes it from siblings like jira-key-shape and figma-url-shape by naming the specific domain. However, it does not specify which input parameter should contain the URL, leaving some ambiguity given the schema has nine unrelated fields.

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?

There is no guidance on when to use this tool versus alternatives such as normalize-url or browser-url-ok. The description does not mention exclusions or provide context for selecting this tool among the many shape-checking siblings.

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