coda_push_button

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

The description adds that the effect depends on the button's configuration and returns a requestId for async mutation tracking, disclosing important behavioral traits beyond annotations which only indicate readOnlyHint=false and openWorldHint=true. No contradiction.

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?

Four sentences with no fluff. The first sentence states the primary purpose. Each subsequent sentence adds necessary detail without redundancy.

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 complexity (4 required params, async behavior, config-dependent effects), the description covers purpose, usage, behavioral notes, and return value (requestId for tracking). Output schema exists but its details are not needed.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds the context that the button must be in a Button-type column, which is not in schema descriptions, providing extra value.

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 'push' and the resource 'button in a Coda table row', and is distinguishable from sibling tools like update_row or trigger_automation.

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 specifies that the button must be in a Button-type column and triggers its configured action, providing clear context for when to use the tool. It does not explicitly state alternatives or when not to use, but the context is sufficient.

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