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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context by specifying the contents (drinks, skills/effects, looks, personas, voices), Dogecoin pricing, and the fact that the menu is also surfaced when entering a room. There is no contradiction with annotations.

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 description is two tight sentences with no filler. The first sentence front-loads the core purpose and content, and the second adds a concise, relevant contextual note about room entry. Every clause 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?

For a zero-parameter tool with no output schema, the description fully specifies what the agent should expect back: drinks with skills and effects, looks, personas, voices, and Dogecoin prices with explanations. Combined with the safety annotations, an agent has enough to invoke and interpret this tool correctly.

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 input schema has zero parameters, so the baseline is 4. The description reinforces that no input is needed by presenting the tool as a one-scan overview, and it explains what the returned data will contain, which is sufficient given the absence of parameters.

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 clearly frames the tool as returning an aggregated menu: 'The whole menu in one scan' followed by the item categories drinks, looks, personas, and voices. It distinguishes itself from sibling list_* tools by covering all categories at once rather than a single category, though it does not use an explicit verb like 'get' or 'list'.

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 implies that this tool is for seeing the complete menu ('The whole menu in one scan') and notes that it is 'Also returned when you enter a room'. However, it does not explicitly state when to choose this over list_drinks, list_looks, list_personas, or list_voices, nor does it name alternatives.

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