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

No annotations are provided, so the description carries the full burden. It does disclose 'No disk access' and notes that some params are 'discarded after the shape check', which gives a hint of non-persistence. However, it doesn't state what the tool returns (boolean? error?), what 'safe' means, or any side effects beyond no disk access. This is minimal transparency for a multi-purpose check tool.

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 sentence, which is concise, but it is under-specified and misleadingly narrows the tool to path checking when it actually accepts many types. The structure doesn't front-load the tool's general purpose or its return behavior, so conciseness here is detrimental rather than helpful.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description is severely incomplete. It doesn't explain what 'safe' means, what the tool returns, how to interpret results, or how the various parameters relate to the tool's operation. An agent cannot correctly invoke this tool without substantial guessing.

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%, but the parameter descriptions are terse and mostly repeat 'discarded after the shape check' without explaining how each parameter is used or what shape is checked. For example, 'City name for a public weather hint' is irrelevant to path safety. The description adds no unifying semantics; it leaves the agent confused about how to set parameters correctly for a specific check.

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 it checks whether a path looks safe, but the tool accepts 9 unrelated parameters (ref, url, city, feed, host, json, path, zone, query) and only mentions path. This is misleading; it doesn't convey that the tool actually performs generic shape checks across many input types. It also doesn't distinguish it from sibling shape-check tools like domain-shape or validate-json, so an agent can't tell what makes this tool unique.

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 on when to use this tool versus alternatives. The description only says 'Check whether a path looks safe' with no context, no exclusions, and no mention of alternative tools. An agent has no basis to decide if this is the right tool for a given input type.

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