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

With no annotations, the description is the only behavioral signal, and it only says 'Parse...'. It does not disclose return format, failure behavior for invalid/non-GitHub URLs, or how it treats the many unrelated optional schema fields (city, feed, json, path, query).

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?

A single nine-word sentence with no filler. The key action and object are front-loaded, and every word earns its place.

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?

Given no annotations, no output schema, and a noisy nine-parameter schema, one sentence is not enough for an agent to know the expected input format or return value. It should at least mention that only `url` matters and what the tool returns for valid/invalid GitHub URLs.

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 description does add a useful mapping from 'GitHub URL' to the `url` parameter, but it provides no guidance about the other eight optional parameters or which ones are relevant.

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'), specific outputs ('owner and repo'), and a specific input class ('GitHub URL'). This clearly distinguishes it from sibling URL/shape tools such as normalize-url or jira-key-shape.

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 GitHub-URL scope implies when the tool should be used, but the description never states an explicit trigger, nor does it mention alternatives or when-not-to-use cases. Selection guidance is left to inference.

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