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

With no annotations, the description must carry the full behavioral disclosure burden. It only states 'parse owner and repo' without specifying output format, error behavior, or how the other 8 parameters are handled. The schema mentions 'discarded after the shape check' for some fields, but that is in the schema, not the description, so the description itself reveals nothing beyond the basic action.

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 sentence, which is concise, but it is under-specified and lacks structure. It does not front-load critical information or explain the tool's scope relative to its schema. The brevity is not a strength given the complexity of the schema.

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?

For a tool with 9 parameters and no output schema, the description is severely incomplete. It does not explain return values, how to invoke the tool correctly, which parameters are required (none are, but still), or what happens with the non-URL inputs. An agent cannot reliably use this tool based on the description alone.

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 schema coverage is 100% (baseline 3), the description adds no parameter meaning and actually misleads by implying only a URL matters. It does not clarify which of the 9 parameters are relevant to 'GitHub URL' parsing or how they relate. The schema descriptions are present, but the tool description fails to connect them to the tool's purpose, so an agent cannot determine which inputs are 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 states a clear verb and resource ('Parse owner and repo from a GitHub URL'), but it is inconsistent with the input schema, which contains 9 unrelated parameters (city, feed, json, path, etc.). This creates ambiguity about what the tool actually does and does not distinguish it from siblings like domain-shape or jira-key-shape beyond the GitHub reference.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention typical use cases, prerequisites, or exclusions. An agent has no way to know when to choose this over domain-shape or other shape-check tools.

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