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

Annotations are absent, so the description carries the full burden of behavioral disclosure. The description only says 'parse' without stating whether it performs network access, how it handles invalid URLs, or whether it discards other input parameters (though the schema hints at 'discarded' for some). No mention of errors, side effects, or return format.

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 extremely concise (a single short sentence), which is positive, but it lacks structure and essential context. It does not front-load key information like the output (owner/repo) or the fact that only the URL is used. It is under-specified rather than effectively concise.

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 the tool has 9 parameters and no output schema, the description is inadequate. It does not explain what the tool returns (owner and repo pair), how to interpret success/failure, or that it ignores most parameters. The description is too minimal for an agent to correctly invoke the tool without additional assumptions.

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?

While schema description coverage is 100%, the tool description adds no value beyond the schema. It does not clarify that only the 'url' parameter is relevant, and the presence of 8 unrelated parameters (ref, city, feed, etc.) is misleading. The description could have stated that other fields are ignored, but it doesn't, leaving agents unsure which parameters matter.

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 resource ('owner and repo from a GitHub URL'), which clearly distinguishes it from URL-checking siblings like browser-url-ok or normalize-url. However, the input schema includes many unrelated parameters (city, feed, json, etc.) that are not mentioned in the description, creating potential confusion about the tool's actual scope.

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 provides no guidance on when to use this tool versus alternative URL-related tools. It does not mention scenarios where parsing owner/repo is needed, nor does it exclude cases like non-GitHub URLs or redirects. No alternatives or exclusions are given.

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