get_action_io

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

The description explains the core behavior: 'Fetches content from inputsLink/outputsLink URLs.' With no annotations, this is helpful but insufficient. It does not disclose potential side effects, authorization requirements, rate limits, or the nature of the fetched data (e.g., size limits, pagination).

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 sentences that cover purpose, technical detail, and usage motivation. It is front-loaded with the action and provides essential information without unnecessary words.

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 has 7 parameters and no output schema, the description should explain what the returned data looks like (e.g., format, structure). It only mentions 'actual input/output data' which is vague. Users debugging transformation issues need to know the response shape, making this description incomplete.

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%, so baseline is 3. The description adds value by clarifying that 'workflowName is required for Standard SKU,' which provides critical usage context beyond the schema. The type enum is already clear from the schema.

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 'Get the actual input/output data for a run action' and specifies it fetches from inputsLink/outputsLink URLs. It differentiates the tool's purpose from generic run data retrieval but doesn't explicitly distinguish it from action-specific siblings like get_action_repetitions or get_action_request_history.

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 provides context by stating 'For Standard SKU, workflowName is required' and labels the tool as 'Essential for debugging data transformation issues.' However, it lacks guidance on when not to use it or how it compares to alternatives among the many sibling tools.

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