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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere and the description adds nothing on top. Worse, it lists the states as '(kept, skipped, unsorted)' while the schema enum is pending/kept/skipped/committed — 'unsorted' is not a real state, which can mislead the agent. Pagination/return behavior is also absent.

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 with no filler; the verb and resource come first. The phrase 'to show the person or to sort' is slightly vague and the parenthetical state list is inaccurate, but structurally it is tight.

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?

With no output schema, 3 parameters at 33% coverage, and one enum, the description carries the burden of explaining return shape and the offset paging behavior — and does neither. The incorrect state list compounds the gap, leaving the agent under-informed for a non-trivial read operation.

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 only 33% (just the 'state' enum is documented), and the description does not compensate: it never explains offset/limit-style paging despite an 'offset' parameter, and its enumeration of states contradicts the schema's own enum values. 'ids' is mentioned as returned content, not as a parameter, so it adds nothing about inputs.

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 and resource: 'Read an import's entries with their ids and states.' The trailing 'to show the person or to sort' hints at the boundary against sibling sort_import, so the agent can partially distinguish it from commit_import/sort_import/start_import without opening the schema.

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?

Usage is only implied by the phrase 'to show the person or to sort' — a read/browse purpose. It never explicitly states when to call this versus sort_import or commit_import, nor any prerequisites (e.g. that an import must exist). Adequate but leaves routing to inference.

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