Get data store entries

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

Annotations already declare readOnlyHint=true, and the description adds a useful behavioral constraint: '$top not supported server-side.' This is helpful but not a rich disclosure; it does not mention auth requirements, response behavior, or other limitations beyond the $top note.

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?

Two short sentences with no filler. The core purpose is front-loaded and the unsupported-$top caveat is clearly separated at the end. Every word earns its place.

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 tool is simple and the description conveys the core purpose and one important gotcha, but with no output schema and no parameter explanations, an agent has limited guidance on how to construct valid skip/filter/select/orderby values. The note about $top is useful but does not fill the parameter-documentation gap.

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%, and the description does not explain 'skip', 'filter', 'select', or 'orderby'. The $top note hints at pagination behavior, but the description fails to compensate for the complete lack of parameter documentation in the schema.

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 states a specific verb ('List') and a specific resource ('data store entries'), and the parenthetical clarifies what those entries are ('persisted key-value records across messages'). This is clear, though it does not explicitly differentiate from sibling tools by name.

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 clear context for when the tool is relevant: listing persisted key-value records across messages. There is no explicit alternative or exclusion, but no obvious sibling tool competes for this exact resource, so the guidance is adequate.

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