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

With no annotations, the description carries the full burden and it discloses meaningful behavior: scope risk is evaluated independently of advisory risk, and an unvetted publisher requesting shell/filesystem access is refused even with a clean record. It also instructs the agent to follow the returned `agent_action`, which is a direct behavioral directive.

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?

Three sentences, each essential: the trigger, the risk model, and the follow-up action. The core instruction is front-loaded with 'BEFORE recommending...' and there is no 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 single-parameter check tool, the description covers when to use it and how to handle the result via `agent_action`. The lack of an output schema is partially mitigated by that instruction, though exact response fields beyond `agent_action` remain unspecified.

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% and the schema already provides the server_id example. The description does not add parameter-level detail beyond implying that the server being checked is the MCP server under consideration.

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 verb and resource: before recommending a community/unofficial MCP server, check it here. The scope is clearly limited to MCP servers, distinguishing it from sibling tools like vdb_check_package and vdb_search.

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?

It gives an explicit trigger condition ('BEFORE recommending a community/unofficial MCP server'), making the when-to-use clear. It does not name alternative tools for other asset types, but the scope restriction implies when not to use it.

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