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

With no annotations provided, the description carries the full burden and does a good job: it clearly indicates this is a read-only introspection tool and even discloses the server's boundary ('it never adjudicates'). It does not discuss output format, but the listed fields give a reliable expectation of what the call will return.

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, well-structured sentence that front-loads the core purpose and then provides a concise bullet-like list of return contents. There is no redundancy or filler.

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 zero-parameter, no-output-schema introspection tool, the description is complete: it names the server, the contents of the response, and the key boundary. An agent has enough information to invoke the tool correctly and understand what it will get back.

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?

The tool has zero parameters, so parameter semantics are not applicable beyond noting that no input is required. The description adds the necessary context about what the returned self-description contains, more than compensating for the absence of parameters.

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 clearly states a specific verb ('Return') and resource ('TrustAI Verification MCP self-description'), and enumerates the exact contents returned. It is obviously distinct from sibling tools like get_health or list_checks, which are operational rather than descriptive.

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 the tool is for retrieving an overview of the server's purpose, tools, and boundaries, but it does not explicitly state when to choose it over alternatives. An agent can infer the use case from the listed contents, yet there is no direct guidance or exclusionary language.

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