smartsuite_query_records

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

The annotations already declare readOnlyHint: true, confirming this is a safe read operation. The description adds no further behavioral context (e.g., no mention of side effects, rate limits, or response structure). Since annotations suffice, the description provides minimal added value beyond confirming the read-only nature.

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 two sentences: the first states the purpose and method, the second provides a crucial prerequisite action. It is front-loaded and contains no redundant information. Every sentence earns its place.

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?

The tool has nested parameters (filter object) and no output schema. The description correctly advises on prerequisite knowledge (field slugs) but does not explain the response format, pagination behavior, or how the filter object maps to results. While parameter documentation is thorough, the overall behavior remains somewhat opaque without additional context.

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 88% (7 of 8 parameters have descriptions), so the schema already explains most parameters. The description does not add parameter-specific details beyond the overall purpose. It includes a hint about field slugs, which is indirectly useful but not parameter-specific. Baseline 3 is appropriate given the high schema 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?

The description clearly states the action ('Query records') and the resource ('using a structured SmartSuite filter'). This distinguishes it from sibling record tools like smartsuite_list_records (which lists all records) and smartsuite_search_records (which likely uses search syntax). The verb and resource are specific and unambiguous.

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 explicitly advises to 'Use smartsuite_describe_application first to learn field slugs and valid values for choice fields', providing a clear prerequisite. However, it does not specify when not to use this tool versus alternatives like smartsuite_list_records or smartsuite_search_records. The guidance is helpful but lacks exclusions.

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