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

The annotations provide comprehensive behavioral signals (readOnlyHint, destructiveHint, idempotentHint). The description adds minor helpful context regarding the `app_url` being present in the response, but doesn't add much beyond the structural metadata already provided.

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?

While a little verbose, the structure is logical, starting with the core purpose and ending with the technical context (UI link and access rights). The information density is appropriate for a high-level description.

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 is complete for its intended purpose. It confirms the resource scope (only the user's saved items), the required identifier, and the necessary UI context (`app_url`) for the agent to follow up.

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?

Since schema coverage is 100%, the baseline is 3. The description adds value by explaining the multiple possible sources for the required `mandate_id` (i.e., from `list_mandates`, a Gambit row, or an activity row).

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 intent is to retrieve a specific 'Gambit' (mandate). By requiring a `mandate_id`, it distinguishes this retrieval operation from listing or creating mandates.

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 provides crucial usage guidance by specifying that if the ID belongs to another user, it will return a 404 error. This defines the scope and limitations of the tool for the agent.

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