list_integration_workspaces

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world. Description adds specific return fields ('total plus workspace ids, names, enabled state, usage limits, and rate limits') and error behavior (403 for non-Enterprise). Adds significant value beyond annotations.

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?

Three concise, front-loaded sentences. No redundant information. Each sentence adds value: purpose, use cases, and plan restriction/error code.

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?

For a list endpoint with pagination and an output schema, the description covers what the tool returns, error cases, and plan restrictions. Annotations cover safety. Complete for the tool's complexity.

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 parameters with descriptions (100% coverage). The description does not add extra parameter information beyond what is in the schema. 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?

Clearly states verb 'List' and resource 'workspaces that can use an integration' with additional detail 'with their limits'. Distinguishes from siblings like list_workspaces by specifying the integration context. Also gives concrete use cases: 'audit access or confirm per-workspace cost and rate settings'.

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?

Explicitly says 'Use this to audit access or confirm per-workspace cost and rate settings'. Also warns about enterprise gating and 403 error on non-Enterprise plans. Does not mention alternatives, but the context of when to use is clear.

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