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

No annotations are provided, and the description does not disclose any side effects, error handling, or limitations. It only says 'parse,' implying a read-only operation, but gives no details on what happens with invalid URLs or unexpected inputs.

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 gets to the point without wasted words. Its structure is simple and clean, though it could benefit from additional context without becoming verbose.

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 lacks an output schema and does not explain how the 9 parameters are used or which are required. This leaves agents without essential information about how to call the tool effectively 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?

The schema includes 9 optional parameters, but most descriptions are unrelated to parsing GitHub URLs (e.g., 'City name for a public weather hint,' 'Public RSS or Atom URL'). These misleading parameter descriptions actively confuse agents about which inputs are relevant, failing to add meaningful semantics.

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 parses the owner and repo from a GitHub URL, naming the exact resource and action. However, it omits details about the output format or any edge cases, so it's slightly lacking in completeness.

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 similar URL-shape tools like figma-url-shape or jira-key-shape. There's no mention of typical use cases, prerequisites, or conditions that would make this tool the right choice.

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