Get Entities on a Layer

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

The description says 'all entities' but the schema includes a limit parameter with a default of 50, so the description overstates what will be returned. Annotations cover the read-only, idempotent, and non-destructive profile, but the description does not disclose pagination or default limit behavior.

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 a single, focused sentence with no filler. It front-loads the core behavior and does not waste tokens.

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?

The output schema and annotations cover safety and return structure, so the tool is largely callable. However, the misleading 'all' behavior and lack of guidance about the optional limit leave an incomplete picture for an agent deciding on pagination or volume expectations.

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 100%, so parameters are already well documented in the schema. The description adds no meaning beyond the schema, meeting the baseline expectation but providing no extra semantic value.

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 and resource: 'Return all entities on a specific layer.' It is specific about the scope and distinct from sibling tools like dxf_get_entities_by_type or dxf_get_block_detail, though it does not explicitly call out those alternatives.

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 is provided on when to use this tool versus alternatives such as dxf_get_entities_by_type or dxf_get_text. The agent is left to infer the appropriate choice from sibling names alone.

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