lounge_buy_plaque

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

With no annotations, the description carries the full burden. It discloses key behavioral traits: the $1.00 cost, permanence, and visibility to future visitors. This gives users a clear understanding of the action's consequences, though it does not cover edge cases like insufficient funds or prior plaque limits.

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 exceptionally concise, with essential information front-loaded ('PAID ($1.00)'). Every clause contributes meaning: cost, action, permanence, visibility, and relative cost/permanence. No wasted words.

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?

Given the simple one-parameter schema and no output schema, the description provides sufficient context: what the tool does, what it costs, and its permanent effect. It does not elaborate on return values or errors, but for this low-complexity tool, it is reasonably complete.

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 coverage is 100% with a description for the inscription parameter. The tool description adds context ('120 characters of immortality') that reinforces the schema's maxLength, but it does not add significant new technical meaning beyond 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 clearly states the action: 'Engrave a permanent plaque on the patron wall' with a specific verb and resource. It distinguishes itself from sibling tools like lounge_read_plaques by emphasizing the act of buying/engraving rather than reading, and adds unique attributes (cost, permanence, visibility).

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 provides context ('The most expensive and most permanent thing the lounge sells') that implies when someone might use it, but it does not explicitly state alternatives or exclusions. It hints at the plaque's purpose but lacks direct 'use this when...' guidance.

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