fm_cleanup_test_data

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

No annotations provided, so the description must disclose behavioral traits. It mentions deletion but does not state that it is irreversible, the scope of deletion, or any permission requirements. The requirement for tagField is noted, but other behavioral aspects are missing.

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 extremely concise, consisting of one clear sentence and a note. It is front-loaded with the action and provides essential information without fluff.

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 3 parameters, no output schema, and no annotations, the description is too minimal. It lacks details on return values, error behavior, and how the deletion is performed (e.g., whether it's a batch operation). More context is needed for a destructive tool.

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 only 33% (only tagField described). The description adds that tagField 'must be an existing text field', but does not explain the 'table' or 'tag' parameters beyond their names. No default or pattern explanation is given beyond the schema.

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 (deletes), the resource (test records), and the identification method (marked with a specific tag). It distinguishes from sibling tools like fm_delete_record which target individual records.

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 for cleanup of test data via a tag, but does not explicitly state when to use this tool versus alternatives like fm_delete_record or fm_batch. It gives a condition (tagField must exist) but lacks when-not guidance.

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