exact_list_entity_records

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond those: only 'allowed' records are accessible, fields are validated, a safe continuation cursor is provided, and raw OData is not accepted. This enriches the agent's understanding without contradicting the annotations.

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, front-loaded with the action and resource, and every clause adds useful information. There is no fluff or repetition.

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 the tool's high parameter complexity and lack of an output schema, the description provides a solid high-level map but omits details such as valid entity names, select-field semantics, cursor/skip interplay, and explicit sibling differentiation. Annotations reduce the safety burden, but the description is not fully complete for a first-time caller.

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 0%, so the description must compensate for missing parameter explanations. It adds semantic meaning for filters, ordering, limits, and cursor-based continuation, and clarifies that filters are structured rather than raw OData. However, it does not explicitly describe the 'entity' or 'select' parameters, leaving those to inference.

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 ('Read'), the resource ('entity records'), and the key capabilities: structured filters, validated fields, ordering, limits, and a continuation cursor. This distinguishes it from sibling metadata tools like exact_list_entities or exact_get_entity_schema. However, it does not explicitly name a sibling alternative such as exact_get_entity, so it stops short of a perfect 5.

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 implies usage: call this when you need to read permitted entity records with filtering and pagination. It does not explicitly state when to prefer a sibling tool, nor does it provide alternatives beyond the rejection of raw OData.

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