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

With no annotations, the description discloses return types (signed cert, badge SVGs, leaderboard position) and that it's free and instant. It does not mention side effects, but actions are self-explanatory and non-destructive.

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?

Five sentences, front-loaded with main purpose, each sentence adds clear value. No redundancy or fluff.

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?

Covers action parameters and return types adequately. No output schema needed. Lacks error handling or rate limits, but for a simple free tool it's sufficient.

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 covers all 5 parameters with descriptions. The description adds context on how to use each parameter with specific actions and notes optionality of email and use_case, exceeding schema alone.

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 it gets or issues a Zambo MCP Verified certificate and lists three actions. However, it does not explicitly differentiate from sibling tools like zambo_check or zambot_verify, which may have overlapping functionality.

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 explicitly tells when to use each action with parameter requirements, e.g., 'Call with action='check' + project_url'. It also mentions no auth required, providing clear usage context.

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