fm_delete_record

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete a record' signals a destructive write, but it says nothing about irreversibility, required permissions, side effects on related data, or whether confirmation is needed—critical omissions for a deletion tool.

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 single sentence is structurally concise and front-loaded, but it is under-specified rather than efficient. For a destructive tool with three required parameters and no annotations, a bare 'Delete a record' fails to earn its place by conveying necessary context.

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 no annotations, no output schema, three required parameters, and destructive semantics, the description is completely inadequate. It omits permissions, reversibility, error behavior, and any usage context an agent would need to invoke it safely.

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 100%, so the schema already documents database, layout, and recordId fully. The description adds no additional meaning about parameter format, constraints, or relationships beyond what the schema provides, so baseline 3 is appropriate.

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?

State a specific verb ('Delete') and resource ('record'), so the core operation is unambiguous. However, it does not differentiate this tool from the many other record-level siblings (fm_update_record, fm_create_record, fm_query_records), leaving the agent to infer the distinction from the name alone.

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 provides no guidance on when to use this tool versus alternatives such as fm_update_record or fm_create_record, and it offers no warnings or prerequisites for a destructive operation.

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