update_action

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

No annotations are available, so the description bears full responsibility for behavioral disclosure. It only states 'Update an existing action' without detailing side effects, permission requirements, or what happens when updating specific fields like 'archived' or 'template'.

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 a single, clear sentence with no redundancy. However, it could be slightly more informative without becoming verbose.

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 complexity of the input schema (nested object with many optional fields), the lack of annotations, and no output schema, the description is inadequate. It does not explain update behavior, partial updates, or field constraints.

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?

The description does not mention any parameters. With 0% schema description coverage, the description must compensate, but it fails to add any value beyond the schema's own property 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?

The description clearly states the verb 'Update' and the resource 'existing action' in Metabase. It distinguishes from sibling tools like create_action, delete_action, and get_action by specifying the update operation on an existing resource.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., create_action or delete_action). There is no mention of prerequisites, such as needing an existing action ID, although the schema requires it.

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