mdpa_get_entities

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that at most 'limit' rows are returned along with a total count and truncation flag, which is critical beyond the schema. It still does not explicitly state that the operation is read-only or describe error behavior, leaving a minor gap.

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?

Three tight sentences are front-loaded with the core purpose, then parameter guidance, then output truncation behavior. Every sentence adds necessary information with no redundant or filler content.

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 a read-only list tool with an output schema already covering return values, the description supplies enough context about filtering and pagination. It does not mention permissions or error handling, but for this tool type those are relatively minor omissions.

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, and it does well by explaining the semantics of ids (explicit filtering), kind (enum values and default), entity_type (with an example), sub_model_part (dotted path), and limit (row cap). The required 'path' parameter is only implied by context ('a .mdpa') rather than explicitly described.

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?

States a specific verb ('List') and precise resource ('elements, conditions or geometries of a .mdpa') along with the returned attributes (type, property id, node connectivity). This distinguishes it from sibling tools like mdpa_get_nodes, which handles nodes rather than entities.

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 explains the filter parameters (ids, entity_type, sub_model_part) and the default kind, which implies how to use the tool. However, it gives no explicit guidance on when to choose this tool over alternatives such as mdpa_get_nodes or mdpa_inspect, nor any exclusions or prerequisites.

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