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

No annotations are provided, so the description alone must carry behavioral disclosure. It only states the parse operation and does not disclose that many of the nine parameters (city, feed, json, path, query, etc.) are discarded, nor does it describe error behavior for invalid or non-GitHub URLs. The parameter descriptions in the schema mention discarding, but the tool description itself adds no such context.

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 or repetition. It is efficient for stating the core purpose, though it may be too terse given the complexity of the nine-parameter schema and the lack of annotations.

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, so the description should explain the return value, but it only says 'parse owner and repo' without specifying the output format or behavior on invalid input. It also fails to reconcile why unrelated parameters like city, feed, host, json, path, and query are accepted, leaving the agent uncertain about what actually gets used.

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 description coverage is 100%, so the baseline is 3. The tool description adds little per-parameter meaning beyond implying that the 'url' field is the relevant one for parsing a GitHub URL. It does not clarify why the other eight parameters are accepted, but the schema descriptions do document each field's role.

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 ('Parse') and a specific resource ('owner and repo from a GitHub URL'), making the tool's core function clear. It also differentiates from sibling shape tools by focusing on GitHub, though it does not mention how it differs from URL-handling siblings like normalize-url.

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?

Usage is implied: an agent can infer to use this tool when it needs to extract a GitHub owner and repository from a URL. However, the description gives no explicit routing guidance, prerequisites, or exclusions, and it does not mention alternatives such as normalize-url or browser-url-ok.

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