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. It only says 'parse' but does not explain what happens to the nine optional parameters (e.g., city, zone, json), whether they are ignored, or what the return value is. The broad schema and narrow description leave significant misalignment and uncertainty.

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 short sentence that is concise and front-loaded, but it lacks the supporting details necessary for a tool with a broad, overloaded schema. The brevity undermines its helpfulness despite the clean phrasing.

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 a schema with nine optional parameters spanning many domains, no output schema, and no annotations, the description is dramatically insufficient. An agent has no idea whether to pass a city, zone, JSON text, etc., and what the tool actually returns in each case.

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?

The schema already provides descriptions for all nine parameters, so baseline is 3. The tool description adds slight specificity for the URL parameter (GitHub URL, owner/repo) but provides no additional meaning for the other eight parameters.

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 action and target: 'Parse owner and repo from a GitHub URL.' This clearly differentiates it from sibling shape tools like figma-url-shape or jira-key-shape by naming the exact resource (GitHub) and the derived output.

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 implies the tool should be used when a GitHub URL needs owner/repo extraction, but it provides no explicit when-not guidance or alternatives. An agent must infer the correct sibling because the description does not mention exclusions or conditions.

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