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

With no annotations present, the description carries the burden and does disclose the key behavioral trait: it is a free read with no monetary cost, contrasted against the paid siblings. It does not cover auth/permission requirements or rate limits, which leaves a small gap for a no-annotation tool.

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?

Front-loads the resource before the routing instruction, and every clause carries content. The world-specific phrasing ('room-service menu', 'Agent Meal dishes') is dense but not padded, and no sentence is wasted.

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?

No output schema exists, so the description must describe returns, and it does name the three result areas (dishes still sendable, room level, next upgrade price). Combined with the free-vs-paid framing, an agent has enough to call it correctly; only permission/limit details are absent.

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?

There is a single parameter and schema description coverage is 100%, so the schema already fully documents agentId. The description adds no format, range, or lookup-syntax detail beyond restating that it identifies one ERC-8004 agent, so the baseline of 3 applies.

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?

Names the resource (room-service menu for a single ERC-8004 agent on Arc) and enumerates what the read returns: available Agent Meal dishes for the season, the room level, and the next upgrade with its live price. It also explicitly separates itself from the write-path siblings room_order_meal and room_upgrade, so an agent can route without opening the schema.

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?

States the usage condition directly: this is the free read path, while ordering/upgrading costs money and lives in room_order_meal and room_upgrade. The when-to-use vs alternatives decision is fully explicit.

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