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

With no annotations, the description carries the disclosure burden. It states the core behavior (parsing a GitHub URL into owner and repo), but it does not explain what happens with invalid URLs, what the return shape is, or that the many other accepted parameters are effectively ignored for this operation.

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 front-loaded sentence with no filler. The verb and object appear immediately, and every word contributes to the meaning.

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 and no annotations, so the description must explain what the tool returns and how it behaves on edge cases; it does neither. The schema also lists nine unrelated optional parameters (weather, timezone, JSON, query, etc.), and the description does not clarify why those exist or confirm that only 'url' is used, leaving an agent uncertain about 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?

Schema description coverage is 100%, so the schema already documents all nine parameters and their discard semantics. The description adds no new parameter-level detail, but it does identify the meaningful input domain (GitHub URL), which is enough for the baseline score.

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'), making the tool's function immediately clear. It also differentiates it from sibling shape tools such as figma-url-shape and jira-key-shape without needing to inspect the schema.

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 'GitHub URL' — an agent will know to reach for this tool when it needs owner/repo from a GitHub URL. However, it does not explicitly name alternatives or state when not to use it, so the routing 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.