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

No annotations are provided, so the description must carry the full behavioral burden. It adds meaningful caveats (public data only, returns records and links, not advice/recommendation/invitation) but says nothing about permissions, rate limits, error behavior, or what 'open one locker' entails operationally. The disclaimers are useful but the core behavioral profile is thin.

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?

The first two sentences are well front-loaded and efficient. The third sentence is a string of negations ('Not advice, not a recommendation, not an invitation to act') that reads as boilerplate disclaimer rather than actionable tool guidance, diluting the conciseness.

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, no annotations, and 0% schema coverage, the description must do all the work, yet it omits return format, pagination, error cases, and lookup semantics. The disclaimer about 'not advice' is present but substantive operational completeness is lacking for an explorer/retrieval tool.

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% for the single 'handle' parameter. The description mentions '@handle', implying the format includes an @ prefix, which does add minor meaning beyond the bare string type in the schema. However, with no further detail on format, case sensitivity, or lookup semantics, this is baseline for a single-param tool.

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 says it opens a public locker by @handle on bommel.bot, which gives a verb and resource, but 'locker' is an idiosyncratic term that isn't clearly differentiated from siblings like get_public_bommel or search_feed. An agent can guess this retrieves public data for a handle but can't confidently distinguish it from get_public_bommel without more context.

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 only usage constraint is 'Never private library data', which tells the agent what not to target but gives no positive guidance on when to use this over get_public_bommel or search_feed. No prerequisites or alternatives are named.

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