get_records

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

Discloses read-only nature, filter operators, and two error conditions. With no annotations, this provides useful behavioral context beyond the basic purpose.

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 focused sentences. First states purpose, second adds critical detail on filters and constraints. No wasted words, though slightly more structure could help.

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?

With 5 parameters and no schema descriptions, the description should cover more. Filters are well-handled, but major parameters like entity, fields, and ordering are omitted.

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%. Only the 'filters' parameter is described (structure and operators). Other parameters (limit, entity, fields, order_by) lack any textual explanation.

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 'Read rows from one entity,' specifying the action and resource. Distinct from siblings like list_entities or describe_entity.

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 explicit guidance on when to use this vs. siblings. Only mentions constraints (PII blocking, cross-entity references) but not relative advantages or contexts.

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