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

The description discloses what the tool does not do: 'does not read or import local files and does not start work or a build.' This clarifies side effects and non-actions, complementing the annotations (idempotent, 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?

The description is concise, two sentences, with no unnecessary words. It is well-structured and focused on the essential information.

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?

The description gives enough context: what it does, when to call, and what it avoids. Since no output schema is provided, explaining return values is not required. The description is complete for the tool's intended use.

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 schema already provides full descriptions for both parameters (project_id and approval). The description adds context about the one-time choice but does not significantly enhance parameter understanding beyond the schema coverage, so baseline 3 is appropriate.

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 the tool records a one-time choice to use a client with a specific project. It uses a specific verb ('Record') and resource ('choice'), distinguishing it from sibling tools like listing or updating projects.

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?

Provides explicit guidance on when to call: 'Call only after the person approves in the inline card or explicitly in chat.' This gives a clear condition and prerequisite, effectively guiding usage.

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