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

Beyond the readOnly/idempotent annotations, the description discloses the decision vocabulary, the full set of returned fields, that it never contacts the endpoint, that reachability is not safety, and that no API key is needed. These are real behavioral facts an agent needs before calling.

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?

It leads with the core decision and is front-loaded with the most important facts. It's dense, and enumerating all return fields slightly exceeds what's needed given the output schema, but nothing is wasteful.

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 one-parameter assessment tool with annotations and an output schema, the description covers purpose, the decision model, safety caveats, and data provenance. An agent has everything required to call it and interpret the result.

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 single parameter is fully documented in the schema (100% coverage), including the exact-URL and never-contacted semantics. The description adds little about the parameter beyond what the schema already states, so baseline 3 applies.

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 and resource: an immediate use-or-avoid decision about an AI agent or MCP server endpoint, framed for an agent deciding whether to call it. It clearly differs from CRUD-style siblings like get_agent and list_agents, though it never names them 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 intended moment of use is explicit: 'for an agent deciding whether to call it.' No exclusions or named alternatives (e.g., check_agent_trust) are given, so the agent must infer which sibling to prefer.

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