get_action

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

Without annotations, the description provides no behavioral traits beyond the basic retrieval. It does not disclose side effects, permissions, rate limits, or error handling (e.g., what happens if the ID is not found).

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—a single sentence with no wasted words. However, it could be more informative while remaining succinct, such as mentioning the return type or typical use case.

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 lack of output schema and annotations, the description is incomplete. It does not explain what an 'action' is in Metabase, what the output looks like, or any usage context, making it insufficient for an AI agent to use confidently.

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 adds minimal value beyond the input schema. It repeats that the tool retrieves 'by ID', but the schema already describes the 'id' parameter as 'Action ID'. With 0% schema description coverage, the description should compensate, but it fails to elaborate.

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 action is to 'Get an action by ID from Metabase', specifying the verb and resource. However, it does not differentiate from sibling tools like 'get_action_execute_form' or 'list_actions', which cover related but distinct operations.

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. The description lacks any context for selection among the many 'get_*' tools, such as 'get_action_execute_form' or 'list_actions'.

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