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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only states the parse action but does not disclose side effects (e.g., network access, read-only nature), limitations, or the discarded parameters. The schema hints that many parameters are 'discarded', but the description does not explain this behavior, leaving the agent uncertain about what happens.

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 fluff, which is concise. However, it is under-specified to the point of being unhelpful, and there is no front-loading of critical constraints or usage context. It earns a mid-range score for brevity but lacks the substance needed for effective structure.

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 9 parameters, no required fields, and no output schema, yet the description provides only a one-line statement of intent. It omits any information about return format, error handling, or how to properly invoke the tool with the available parameters. This is completely inadequate for a tool with such a broad schema, leaving the agent without enough context to call it correctly.

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 coverage is 100%, so each parameter has a description, but those descriptions are generic (e.g., 'HTTPS URL to normalize or cite') and do not clarify that 'url' is the GitHub URL to parse. The tool description adds no guidance on which of the 9 parameters are relevant for the stated purpose, failing to compensate for the schema's ambiguity. The parameter descriptions do not map to the tool's stated function, so the description adds minimal semantic value.

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 a specific resource ('owner and repo from a GitHub URL'), which clearly identifies the tool's purpose and distinguishes it from sibling shape tools like domain-shape or jira-key-shape. Even though the schema includes many unrelated parameters, the description itself is unambiguous about the core function.

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 gives no guidance on when to use this tool versus alternatives such as normalize-url, browser-url-ok, or fetch-status. There is no mention of prerequisites, context, or exclusions. An agent would have to infer the appropriate use case from the name alone.

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