Run Tool

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

The annotations already declare destructiveHint=true, and the description adds crucial context by detailing the 'confirm' parameter's role in approving destructive actions. This goes beyond the annotation by explaining the execution workflow, making behavioral expectations transparent.

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 with two short paragraphs and a bullet-style list for parameters. It is front-loaded with the core purpose and quickly provides actionable details without extraneous text.

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 the tool's generic execution role and the presence of an output schema (not shown), the description covers all necessary aspects: how to find the tool, how to pass arguments, and when to confirm destructive actions. It is complete for an agent to use correctly.

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?

Despite 0% schema description coverage, the description adds significant meaning: it specifies that 'tool_name' must be an exact name, explains 'arguments' as a JSON string or dict, and clarifies the 'confirm' parameter's purpose. This compensates for the schema's lack of explanation.

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 'Execute an API tool by name with the given arguments.' This is a specific verb and resource, and it is distinctly different from the sibling tools 'list_toolsets' and 'search_tools', which are for discovery, not execution.

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 'Use search_tools first to find the tool name and its parameter schema,' providing clear context for proper use. It also explains when the 'confirm' parameter is required, which is valuable guidance.

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