list_entities

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

Discloses behavioral traits such as pagination, wildcard filtering, and optional type/layer filters. Since no annotations are provided, the description carries the full burden and does a good job, though it doesn't describe error conditions or ordering.

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?

Single concise sentence with no fluff; all information is relevant and front-loaded. It includes the main action, filters, pagination, and a performance tip 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?

Covers the tool's purpose, filtering behavior, pagination, and a performance tip. Given an output schema exists, return values need not be explained. Overall, a complete and efficient description for a list tool.

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 that entity_type and layer are optional filters capable of wildcards, and that pagination is controlled by limit/offset. This adds semantic meaning beyond the schema, which has no descriptions.

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 type, handle, and layer, and supports pagination and optional filtering. It distinguishes itself from sibling tools like get_entity and get_entity_counts by focusing on bulk listing with filters.

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?

Provides explicit guidance to run get_entity_counts first on large drawings, indicating a specific alternative and context. However, it doesn't mention other alternatives or when not to use this tool, so it's slightly incomplete.

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