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

With no annotations, the description carries the full burden and does disclose the hard 100-record cap, recency ordering, and the behavioral fact that flavor/flair items have no manual effect use and resident tonics remain tied to settlement. It does not say what happens beyond the 100-record window (pagination, truncation) or the return shape.

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 sentences, front-loaded with the read scope and cap before the domain caveats. The second sentence is dense and slightly cryptic ('existing game settlement'), but it earns its place by preventing misinterpretation of effects.

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 no-param, no-output-schema read this is nearly sufficient, but the agent is left unsure what each entry contains (item names? timestamps? effect details?) and whether results beyond 100 are retrievable. These gaps matter because no annotations or output schema fill them in.

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?

The tool takes zero parameters, so there is nothing for the description to clarify; baseline applies. The description correctly adds no fake parameter guidance.

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 ('Read') and resource ('operator Locker purchases and recorded effects') with a clear scope cap ('up to 100 most recent'). It implicitly separates itself from locker_buy and locker_catalog by being a history read, but never names those siblings explicitly.

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 on when to use this instead of locker_catalog, locker_buy, or inventory, all of which sit adjacent in the sibling list. The only directional hint is that flavor items and tonic effects 'stay in existing game settlement', which implies this list is informational rather than actionable, but that must be inferred.

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