fm_query_records

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

Discloses default top (20), max records (10000), pagination via skip, count parameter, and return type (formatted text). Lacks explicit statement that it's read-only, but no contradictions.

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?

Well-structured with Args section, examples, and return value. Slightly verbose but each sentence adds value; no 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?

Covers all parameters, return format, and usage prerequisites. Could mention error scenarios, but overall sufficient for a complex tool with 7 parameters and no annotations.

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?

Despite 0% schema coverage, the description explains every parameter in detail with examples and defaults, adding significant meaning 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?

Clearly states it queries FileMaker records using OData v4, distinguishing from sibling tools like fm_get_record (single record) and fm_count_records (count).

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?

Provides excellent usage guidance: references fm_list_tables for table names, instructs to call fm_get_schema first, and gives detailed filter examples. However, does not explicitly state when not to use this tool (e.g., for single record use fm_get_record).

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