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

With no annotations supplied, the description carries the full burden of disclosing behavior. It does not mention whether the operation is read-only, how invalid or non-GitHub URLs are handled, or whether any normalization or validation side effects occur.

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 is easy to read. It focuses on the core action, but it lacks usage context and parameter clarification, so it is not fully optimal.

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?

There is no output schema, no indication of what the parsed owner/repo result looks like, and no guidance on required inputs. The description is too minimal to give an agent complete context for invoking the tool reliably.

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 parameter descriptions are generic and inconsistent with the stated purpose. The 'url' property is described as 'HTTPS URL to normalize or cite' rather than as a GitHub URL to parse, and the other eight properties appear unrelated or are labeled 'discarded' without explaining their role. Since no parameters are required, an agent cannot confidently determine what input is expected.

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 that the tool parses owner and repo from a GitHub URL, which distinguishes it from sibling shape tools for other domains. However, the input schema includes many unrelated optional fields, which slightly muddies the core purpose.

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 about when to use this tool instead of sibling tools such as figma-url-shape, jira-key-shape, or domain-shape. There are no criteria for selecting this tool over alternatives.

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