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

Annotations are absent, so the description carries full responsibility for behavioral disclosure. It only states 'No disk access' for the path check, but does not explain behavior for other parameters (e.g., whether URLs are validated, whether network calls occur, or what 'discarded' means). This is severely under-disclosed for a tool with 9 parameters.

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, but it is under-specified rather than concisely informative. It omits critical information about the tool's full capabilities, making it ineffective. A concise description should pack essential details; this one leaves too much unsaid.

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 9 parameters, no output schema, and no annotations, the description is drastically incomplete. It does not explain the return value, how parameters interact, or which fields are validated. An agent cannot reliably determine how to invoke this tool correctly, especially given the unrelated parameters.

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%, giving a baseline of 3, but the description adds no extra meaning beyond the schema. It mentions only 'path' and ignores the other 8 parameters, which are each documented in the schema but not synthesized in the description. This omission could lead an agent to think only 'path' matters, undermining semantic understanding.

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 for 'path' ('Check whether a path looks safe'), but the schema lists 8 other parameters unrelated to paths. This creates ambiguity about the tool's actual scope and fails to differentiate it from siblings like browser-url-ok or domain-shape, which are also shape-checking tools. The purpose is only partially clear and potentially misleading.

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 on when to use this tool versus alternatives. There is no mention of preferred scenarios, exclusions, or conditions that would route an agent to this tool instead of a sibling like wiki-title-ok or validate-json. The description offers no usage context whatsoever.

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