fm_get_record

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

Minimal behavior description. With no annotations, description fully carries burden but omits error conditions (e.g., record not found) or return format. Only indicates read operation.

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?

Extremely concise, one sentence with no fluff. Front-loaded with key action and resource.

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 no output schema and no annotations, description covers basic purpose but lacks details on error handling or return behavior. Adequate for simple read, but could be more 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 coverage is 50% (only rowId described). Description adds 'by ROWID' confirming rowId's role, but does not elaborate on 'table' parameter. Baseline 3 with partial coverage.

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?

Clear verb 'Read' and specific resource 'single FileMaker record' with method 'by ROWID'. Distinguishes from sibling tools like fm_query (multiple records) and fm_create_record.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites like needing the ROWID or alternatives for non-ROWID queries.

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