execute_dynamic_tool

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds critical behavioral context: that ORDER_EXEC/DESTRUCTIVE tools need owner_token and confirm=true, which is essential for safe execution. No contradiction with 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?

Two sentences with no redundant information. Each sentence provides crucial guidance: the first states the core function, the second adds important conditions. Highly efficient.

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 no output schema, the description adequately covers purpose, prerequisites, and special cases. Could optionally mention return behavior or errors, but the current completeness suffices for a dynamic tool that delegates execution.

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% with descriptions for both parameters. The description adds value by explaining that for certain tools, arguments must include owner_token and confirm=true, which goes beyond the schema's generic descriptions.

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 'Execute any discovered tool by name with arguments' with a specific verb and resource. Differentiates from siblings by describing the discovery workflow (discover_tools -> get_tool_details -> execute).

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 instructs when to use: after discover_tools and get_tool_details. Provides prerequisites: ORDER_EXEC and DESTRUCTIVE tools require owner_token and confirm=true. Guides the agent on the correct sequence.

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