list_records

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

No annotations are provided, so the description carries the behavioral burden. It discloses that all records for a model are returned, that filtering supports specific operators, and that full record data is included so records can be found by field value. This is substantial behavioral transparency for a read/list tool, though it does not cover defaults or error cases.

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 filler. The core action and model identifier are front-loaded, then capabilities are listed compactly, and the practical use case closes the description without redundancy.

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 list tool with seven parameters and no output schema, the description covers the essential lambda: what it lists, how it identifies the model, filtering operators, sort, pagination, and return richness. It is not exhaustive about defaults or edge cases, but the schema fills in several of those gaps.

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 71%, and the schema already documents the main parameters such as filter, locale, sort, and modelIdOrSlug. The description adds high-level meaning like 'by model id or slug' and 'full data,' but it does not go beyond the schema for individual parameters. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'List the records (entries) of a data model, by the model's id or slug.' It clearly distinguishes from get_record by emphasizing plural listing plus filter/sort/pagination, and it adds the useful behavior that records include full data.

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 gives clear context for when to use the tool: to list records of a model, filter them, sort them, paginate, and locate a record by field value without extra lookups. It does not explicitly name an alternative or state when not to use it, but the usage context is clear enough to route an agent correctly.

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