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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the parsing operation. It does not mention failure behavior for invalid GitHub URLs, whether any network activity occurs, what the parsed result looks like, or that many of the nine schema parameters are ignored/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?

One short, front-loaded sentence with no filler, similar to an efficient tool summary. It earns its place, though it is so terse that it delegates context to the schema and tool name.

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?

Despite a nine-parameter schema, no annotations, and no output schema, the description fails to specify the required input parameter, the return format, or edge-case behavior. An agent cannot confidently know how to invoke this tool or interpret its result beyond a general expectation of owner/repo parsing.

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 met without additional parameter documentation. The description adds value by indicating the url parameter should reference a GitHub repository and that owner/repo are the meaningful results, but it does not map inputs or clarify why the other eight unrelated parameters exist.

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 names a specific verb ('Parse'), the resource ('owner and repo'), and the source ('a GitHub URL'). This clearly distinguishes the tool from sibling shape tools such as jira-key-shape, domain-shape, and figma-url-shape, which target different input formats.

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 description gives no when-to-use or when-not-to-use guidance. It does not explain whether this tool should be preferred over normalize-url, browser-url-ok, or web-fetch for URL-related tasks, leaving selection to inference from the tool name alone.

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