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

No annotations are provided, so the description carries the burden of disclosing behavior. 'Parse' implies a read-only, local operation, which is helpful, but the description does not state what happens with invalid URLs, whether other parameters are ignored, or whether any normalization occurs. This is acceptable but minimal.

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 with no filler. It is front-loaded with the key verb and resource, and every word earns its place.

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?

With nine optional parameters, no required fields, and no output schema, the description is too thin to fully guide an agent. It does not clarify which parameter should be populated, what the return shape looks like, or why the other parameters are present. An agent could reasonably be uncertain whether to pass url, ref, or another field.

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 3. The tool description adds that the relevant input is a GitHub URL and the output is owner/repo, but it does not explicitly map this to the 'url' parameter or explain why eight unrelated optional parameters exist. The schema carries most of the parameter meaning.

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 makes the tool's core purpose immediately understandable. It does not explicitly discuss sibling shape tools, but the GitHub-specific scope helps differentiate it from tools like figma-url-shape or jira-key-shape.

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?

There is no guidance about when to use this tool versus alternatives such as normalize-url, domain-shape, or the other shape tools. No context, prerequisites, or exclusions are provided, leaving the agent to infer the appropriate use case from the name and description alone.

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