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

With no annotations, the description carries the full burden of disclosing behavior. It only says 'parse owner and repo' and does not mention whether any network access occurs, whether inputs are validated, or what side effects (if any) exist.

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 one concise sentence and front-loads the core action. However, it omits any mention of the many optional parameters, making it feel incomplete despite being brief.

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 optional parameters and no output schema, the description leaves too much unspecified. It does not explain which parameters are relevant, what the successful parse produces, or how invalid URLs are handled.

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%, most parameter descriptions are unrelated to the stated purpose. Parameters like city, feed, json, path, and query appear to be copied from other tools, and the description does not explain how they relate to parsing a GitHub URL.

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 a specific verb and resource: parse owner and repo from a GitHub URL. It distinguishes the tool from sibling tools like domain-shape or normalize-url, though it does not describe the output format.

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 given about when to use this tool versus siblings such as github-url-shape, normalize-url, or browser-url-ok. There are no examples, conditions, or exclusions.

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