fm_create_test_record

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

No annotations are provided, so the description carries full burden. It discloses the return value (ROWID) and mentions cleanup, but does not detail side effects (e.g., it is a write operation), permissions, or failure modes. The constraint on tagField is a precondition, not a behavioral trait.

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?

Two sentences with no fluff: first sentence states purpose, second adds a constraint and return value. Every word earns its place, and the description is well front-loaded.

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 tool with 4 parameters, no output schema, and no annotations, the description is partial. It explains the test tag mechanism and return value, but omits details about the 'fields' parameter, optional nature of 'tag', error conditions, and what a ROWID exactly represents. Adequate but not complete.

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 50% (tag and tagField have descriptions). The description adds context that tagField must be an existing text field, but does not explain the 'fields' object or 'table' parameter beyond the schema. It adds marginal value but does not fully compensate for the undocumented parameters.

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 'Creates a test record with a test tag' which distinguishes it from the general create sibling (fm_create_record). It specifies the unique test-related purpose and return value (ROWID) for cleanup.

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 testing due to the test tag and cleanup reference, but provides no explicit guidance on when to use this tool versus fm_create_record or other siblings. No alternative tools or when-not-to-use are mentioned.

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