read_entities

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

The description implies a read operation by listing return fields, but lacks explicit mention of safety or side effects. Annotations have no readOnlyHint, so the description should state it is read-only; it does not.

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, front-loaded with purpose. No unnecessary words. Efficiently conveys core functionality.

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?

Returns fields are described, compensating for missing output schema. However, the 'limit' parameter is not explained, and there is no mention of ordering or pagination behavior. Slightly incomplete given the parameter count.

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?

The description explains the 'class' parameter for filtering, adding value beyond the schema. However, the 'limit' parameter is not described; its constraints are only in the schema (0% schema description 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 tool lists entities with optional filtering by class and specifies the return fields (index, class, model, position). This distinguishes it from sibling tools like inspect_entity, which targets a single 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 guidance on when to use this tool versus alternatives like inspect_entity or read_hooks. The verb 'Lists' implies bulk retrieval, but no explicit context or exclusions are provided.

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