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

With no annotations, the description carries the full burden. It does disclose that this is an active concurrent probe requiring operator authorisation and that the result is a signed verdict, which hints at intrusiveness and auth requirements. It says nothing about runtime, side effects on the target, whether the probe is disruptive, or failure modes.

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?

A single front-loaded sentence with two clauses: the action and the return value. Nothing is wasted, though terms like 'per-surface' are left undefined and add density without clarity.

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?

No output schema exists, and the description only gestures at the return value ('signed per-surface verdict') without explaining what a surface is or how the verdict is structured. For a potentially intrusive security probe with two undocumented required parameters, more context is needed to call it safely and 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 0%, so the description must define both parameters. It loosely maps 'target' to the MCP server and 'authorisation' to operator approval, but never states whether authorisation is a token, signed grant, or scope string, nor what form the target takes (URL, name, endpoint).

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?

States a specific verb and resource: runs a concurrent-client isolation probe against a target MCP server and returns a signed per-surface verdict. That is clearly distinct from get_verdict (retrieve) and verify_receipt (validate), though the description never names those siblings explicitly.

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 phrase 'operator-authorised' implies a precondition: the target must already be sanctioned before probing, which is real usage signal. However, it gives no guidance on when to run a probe versus calling get_verdict or verify_receipt, and no exclusions or sequencing advice.

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