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

With no annotations provided, the description carries the behavioral transparency burden. 'Parse' conveys a read-only, non-mutating operation, but it does not disclose behavior for invalid URLs, return format, or the fact that many input fields are discarded.

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 clear sentence with no filler. The core behavior is front-loaded and every word adds value.

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?

The schema exposes eight fields with no required markers, and there is no output schema or annotations. The one-line description does not tell an agent which inputs actually matter, what the tool returns, or how it handles irrelevant fields, making it incomplete for reliable invocation.

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?

All eight schema parameters already have descriptions, so the baseline is 3. The description adds mild specificity by identifying url as a GitHub URL, but it adds no meaning for the other parameters and may create confusion about why fields like city, feed, and json are present.

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 concrete resource ('owner and repo from a GitHub URL'). This immediately makes the tool's job clear and differentiates it from sibling shape tools like domain-shape 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 purpose implies the tool should be used when a GitHub URL is present and owner/repo extraction is needed. However, it gives no explicit when-to-use conditions, exclusions, or alternatives among the many related URL and shape tools.

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