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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds value beyond them: it enumerates the returned payload fields, discloses the security constraint ('Never print projectApiKey'), and warns that the connector is shared across bots and will not remember the project, forcing the caller to persist credentials itself.

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?

Purpose and trigger are front-loaded, then the return shape, then storage and CLI guidance. It is dense and slightly long, but each sentence carries operational necessity rather than 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?

With no output schema, the description compensates by listing the exact returned fields, and it covers storage, secret handling, and the credential-passing contract. Nothing an agent needs to call and correctly use this tool is missing.

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 the baseline is 3, and the description goes further by clarifying that both projectApiKey and botId must be passed on every call except the credential-fetch tools, which adds semantics the schema's field descriptions only partly convey. It does not add format-level detail beyond that.

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 verb and resource ('fetch your project binding') scoped to QA bots, and the trigger condition (right after the user authorized the TestChimp connector) makes it distinguishable from siblings like get-project-credentials and get-bot-compat.

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?

Gives explicit when-to-use ('right after your user authorized the connector'), a preferred alternative path (CLI via `testchimp bot save-binding`), and the fallback rule (pass projectApiKey and botId on every MCP call). It also names the exception set for the key requirement, leaving little to inference.

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