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

Annotations only declare write/non-destructive. The description adds substantial value beyond that: authentication (JWT), value clamping to /manage bands, and the shape of the response ('each result and the room's settings after'). It doesn't state reversibility or error behavior, so not a 5.

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?

Dense and complete but compressed into a single run-on wall of clauses. It's front-loaded with the JWT requirement, but the field enumeration reads as a dump rather than a structured list, hurting scanability.

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, and the description covers return shape; it also covers auth, all parameters, and constraints for a write tool with a nested-object schema. The only gap is error/failure behavior and reversibility.

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 0% and the schema is an untyped nested object, so the description carries the full burden — and it does, enumerating every permitted key, its type, and constraints (on/off, numbers, Solana mint, USD 1-100000, max 8 entries). This is a genuine compensation for the schema gap.

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?

Specific verb+resource ('Change a Telegram room's settings') and the description explicitly enumerates every configurable key, making it unmistakable against siblings like room_config_get.

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 required JWT and equivalence to room_config_get, which tells the agent when to reach for this vs. reading. No explicit exclusion of unrelated operations, but the pairing with room_config_get supplies clear context.

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