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

With no annotations provided, the description carries full burden but only states the parsing action. It does not disclose error handling, validation behavior, or whether network calls are made, leaving significant behavioral gaps.

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 short (two sentences) but contains redundancy: the second sentence ('When: Parse git@ / https remotes into owner/repo') essentially repeats the first. More efficient consolidation would improve conciseness.

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 tool has one parameter and no output schema. The description covers the core functionality and output format (host/owner/repo) but does not specify the return structure (object vs. string) or provide examples, leaving some ambiguity for the agent.

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 0%, so the description must compensate. It specifies that the URL is a git remote in ssh/https format, adding meaning beyond the raw schema. However, it could be more explicit about expected formats (e.g., full URL vs. partial) and does not describe all potential valid inputs.

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 clearly states the tool parses git remote URLs (ssh/https) into host/owner/repo. It distinguishes from sibling tools like url_parse by specifying 'git remote URL', making the purpose specific and unambiguous.

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 implicitly guides usage by saying 'When: Parse git@ / https remotes into owner/repo,' but it lacks explicit when-not-to-use conditions or alternatives among siblings (e.g., url_parse for non-git URLs).

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