save_audit

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'save', which implies a write operation, but it does not mention whether the tool is idempotent, whether it overwrites existing audits, what permissions are required, or any side effects. This is insufficient for a mutation tool without annotation support.

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, concise sentence with no wasted words. It is appropriately sized for a simple save operation, though it could be expanded to cover essential context. It is front-loaded with the action and object, making it easy to parse.

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?

With 6 required parameters, no output schema, and no annotations, the description is far too minimal. It does not clarify what values are expected for parameters like automation_score, category, or monthly_hours, nor does it describe the overall workflow context (e.g., that the audit must be calculated first). An agent would struggle to populate the parameters correctly without additional information.

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 description coverage is 0%, so the description must compensate by explaining the parameters. It mentions none of the six parameters, their meanings, or their relationships. The schema titles (e.g., 'Automation Score') provide minimal clues, but the description adds no additional semantic value, making it impossible for an agent to understand parameter intent from the description alone.

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 a specific verb ('Save') and a specific resource ('completed automation audit'), and it distinguishes from sibling calculation tools (calculate_time_cost, calculate_automation_score) and retrieval tools (list_audits, get_audit) by indicating a persistence action. The word 'completed' also hints at its position in the workflow.

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 implies usage after an audit is completed, but it does not explicitly state when to use it relative to the calculation tools, nor does it mention prerequisites or alternatives. The guidance is implicit rather than explicit, so it earns a middle score.

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