list_entities

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about pagination, result ordering, permissions, or the fact that a default solution filter is silently applied when 'solution' is omitted. That default-filter behavior is material to interpreting results and is only visible in the schema, not the description.

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?

A single front-loaded sentence naming the resource and both filters, with no filler. It is tightly sized, though the terseness leaves room for the missing behavioral detail noted elsewhere.

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?

For a two-optional-parameter read-only listing tool with full schema coverage and no output schema, minimal description is tolerable. However, with zero annotation coverage the description should at least confirm read-only semantics and the default solution filtering, neither of which it provides.

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 both parameters (prefix, solution) already document their formats, env-var fallbacks, and the empty-string escape hatch. The description merely names 'prefix and solution filters' without adding meaning, so the baseline 3 applies.

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?

Specific verb+resource: 'List Dataverse tables (entities)' clearly states the operation and target. It is distinguishable from siblings like get_entity_schema (single-table detail) and list_solutions, though it never names an alternative. Clear but without explicit sibling differentiation.

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 gives no when-to-use or when-not-to-use guidance and never mentions the alternatives (get_entity_schema, list_solutions) an agent must choose between. Filtering hints ('optional prefix and solution filters') describe capability, not usage conditions.

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