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

The description discloses important behavioral traits: each request queues an approval card and sends exactly once on approve, and there is no standing grant. This goes beyond what annotations (none provided) would offer, giving the agent crucial context about the tool's execution model and safety profile.

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 extremely concise: two sentences that cover purpose, prerequisite, and behavioral constraint. No wasted words; every sentence adds value. It is front-loaded with the core action.

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?

Given that the tool has nested objects and no output schema, the description covers the essential aspects: what it does, the prerequisite (list_integrations), and the approval model. It is mostly complete for a straightforward execution tool, though it could mention expected response or error behavior.

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 description coverage is 100%, so the input schema already documents all four parameters with descriptions. The description does not add extra meaning beyond the schema, such as valid values or format constraints. A baseline score of 3 is appropriate since the schema handles parameter semantics adequately.

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 verb-resource relationship ('Execute a tool on a connected MCP integration') and distinguishes from siblings by referencing the prerequisite tool list_integrations, which is a sibling. This helps the agent understand what the tool does and how it relates to other tools.

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?

The description explicitly advises to first use list_integrations to discover available tools, providing clear context for when to use this tool. It also details the approval requirement (every call needs manager approval, no standing grant), which helps in understanding usage constraints. However, it does not explicitly state when not to use this tool or list alternatives.

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