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

No annotations are provided, so the description must disclose behavior on its own. It states 'parse' but does not describe the return shape, behavior for invalid or non-GitHub URLs, or whether any normalization or validation happens, which the name 'shape' hints at.

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 front-loaded sentence with no filler, which is good. However, given the nine-parameter schema and the implicit 'shape' behavior, a bit more structure, such as naming the operative parameter, would make it appropriately sized.

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 9 optional parameters, no required parameters, no output schema, and no annotations, a one-sentence description is incomplete. An agent cannot tell which optional input to populate, what the result looks like, or why the schema exposes unrelated fields.

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 coverage is 100%, but the schema descriptions are misaligned: 'url' is described as an HTTPS URL to normalize or cite rather than a GitHub repo URL, and many other optional parameters (city, feed, host, json, path, zone, query) are unrelated to parsing owner/repo. The description does not identify which parameter actually drives the parse.

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 names a precise verb and resource: parse owner and repo from a GitHub URL. This is specific enough to distinguish the tool from siblings like normalize-url or figma-url-shape, even without an explicit comparison.

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 instead of siblings such as normalize-url, browser-url-ok, or figma-url-shape, and no mention of exclusions or conditions. The only implicit signal is the tool name.

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