fm_delete_record

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

With no annotations, the description must disclose behavioral traits. It merely states 'Delete', implying a destructive action, but does not mention whether deletion is permanent, cascading effects, permission requirements, or error handling (e.g., record 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 a single, concise sentence with no extra words. It is well-structured and front-loaded, though it could be expanded slightly without losing conciseness.

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 tool is a delete operation with no annotations, output schema, or parameter descriptions, the description is far from complete. It does not explain return values, side effects, error responses, or any conditions under which deletion might fail.

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 coverage is 0%, so the description should add meaning beyond the schema. It only mentions deleting 'by ROWID', giving slight context to the rowId parameter, but does not explain the table parameter or the expected format of rowId. The schema provides basic names and types, but the description does not clarify how to use them.

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 verb 'Delete', the resource 'FileMaker record', and the method 'by ROWID'. It effectively distinguishes this tool from sibling tools like fm_create_record, fm_update_record, and fm_query.

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. It does not mention prerequisites (e.g., needing a valid ROWID), when not to use it, or any context about record ownership or access control.

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