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

No annotations are provided, and the tool-level description only says 'parse'. It does not disclose that most of the nine schema parameters appear unrelated or discarded, nor does it explain validation behavior or side effects, leaving key behavioral traits undocumented.

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, clear sentence with no unnecessary words or redundant information.

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?

With nine optional parameters, no required fields, and no output schema, the one-line description does not explain how to invoke the tool, what it returns, or what happens when the expected GitHub URL is missing or invalid.

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 every parameter has a schema description, only 'url' is plausibly relevant to the stated purpose, and its description says 'normalize or cite' rather than 'GitHub repo to parse'. The other parameters are unrelated or explicitly discarded, and none are required, making it unclear which input is actually needed.

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 uses a specific verb ('Parse') and a clear target resource ('owner and repo from a GitHub URL'), which clearly identifies the tool's function and distinguishes it from sibling shape/URL tools.

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?

The intended use is implied by the description — when owner and repo are needed from a GitHub URL — but it does not explicitly state when to prefer this over sibling tools such as normalize-url or browser-url-ok, nor how to handle non-GitHub URLs.

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