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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds genuinely useful behavior beyond them: deeplinks only appear where the client supports them, and secrets are always placeholders rather than real values. It does not mention any auth or rate-limit considerations, but for a read-only config generator that is a minor gap.

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?

Two tight sentences: the deliverable first, then the usage trigger and the placeholder caveat. Nothing is redundant and no sentence is 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?

An output schema exists, so the description needn't explain return shape. For a two-parameter, read-only tool with full schema coverage and annotations, the description covers purpose, trigger, and the one non-obvious behavior (placeholder secrets) adequately.

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%, so both the slug and client enum are fully documented in the schema, including the 'all clients' default. The description's client list mirrors the enum without adding syntax or selection guidance, 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?

States a specific deliverable (ready-to-paste install config for a FastDrop product's MCP server) and enumerates exactly which clients it covers. This is clearly distinguishable from sibling catalog tools like get_product or search_products.

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?

Explicit trigger: 'Use when the user asks how to install, connect, or add a server found on FastDrop.' That is a clear usage context, though it names no exclusions or alternative sibling tools for adjacent needs.

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