save_form

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

Annotations are absent, so the description must carry the behavioral burden. It only states that the tool saves/writes, without disclosing whether a confirmation dialog may appear, whether all unsaved changes are committed, or what happens when no active form is present.

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 short sentence with no filler. However, 'Save/write' is slightly redundant and the sentence adds limited information beyond the tool name.

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?

For a simple one-parameter tool with no output schema, this description is minimally viable: it names the action and resource. It is still incomplete on failure behavior and when to call it, but the low complexity lowers the required depth.

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 schema provides only a single session_id parameter with 0% description coverage, and the tool description does not mention it at all. The default value hints that it is optional, but the agent receives no explanation of when to supply a different session id.

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 uses a specific verb ('Save/write') and a specific resource ('the active form'), making the core action clear. It doesn't explicitly differentiate from siblings, but no close sibling performs exactly this action; tabular_document_save is for tabular documents and close_form is a different action.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites (e.g., an active form must exist), and no mention of when saving is necessary. The agent must infer usage entirely from the tool name.

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