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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Parse', which implies a local, non-destructive operation, but it does not disclose that the schema accepts eight other unrelated parameters like city, feed, json, and path, nor what happens with invalid GitHub URLs, whether the URL is normalized, or what the parse result looks like. These are 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 one short, front-loaded sentence with no filler. Every word earns its place, and the key action and resource are immediately visible. This is an example of efficient writing, even though more content is needed elsewhere.

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 nine-parameter schema, no annotations, and no output schema, the description is under-specified. An agent cannot tell which parameter to populate, whether the extra parameters are ignored, how invalid input is handled, or what the return value contains. The description is too sparse for the actual tool surface.

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 does add a little param-relevant meaning by clarifying that the 'url' parameter should be a GitHub URL and that owner/repo are the extracted pieces. However, it does not explain how or whether the other optional parameters should be used, leaving invocation ambiguity.

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'), a specific resource ('GitHub URL'), and the expected output ('owner and repo'). This clearly distinguishes it from sibling shape tools like figma-url-shape and jira-key-shape. The only slight ambiguity is that the broad input schema includes many unrelated fields, but the core purpose is 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 implies usage: if an agent needs to extract owner and repo from a GitHub URL, this is the tool. However, it offers no explicit guidance about when not to use it or which alternatives might be better, such as normalize-url for general URL normalization or browser-url-ok for URL reachability checks. The guidance is purely implied by the resource type.

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