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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=false. The description adds genuinely new behavioral facts beyond them: the entry expires, defaults to 15 minutes, and can be removed by a human, and it grants no role or authority. It does not address what happens on a repeat declaration for the same topic/label, which matters given idempotentHint=false.

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?

Two tight sentences with no filler, and the core behavior plus default are front-loaded. 'Independent of bring order' is domain jargon that costs a little clarity for an outside reader, but nothing is padded.

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 mutating tool with destructiveHint=true, no output schema, and 25% parameter coverage, the description covers lifetime and removability but omits what the call returns, whether it requires OAuth-scoped authorization beyond the room_id, and how duplicates behave. Adequate to call, not complete enough to predict consequences.

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 only 25% across 4 parameters, so the description must compensate. It does partially: 'Defaults to 15 minutes' supplies default semantics the schema lacks for ttl_seconds, and 'event-topic' loosely frames topic. But label and the constraints on room_id authorization are left to the schema, and the enum values are never explained.

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?

States a specific verb and resource: records a self-selected, expiring event-topic interest, and scopes it as independent of bring order with a 15-minute default. An agent can tell it is a TTL-scoped interest declaration rather than a permanent role or claim, though no sibling tool is named for contrast.

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?

No explicit when-to-use guidance: nothing says whether to call this instead of weigh_in, propose, or purpose_claim, nor under what conditions declaring an interest is appropriate or inappropriate. The phrase 'independent of bring order' is the only differentiation hint and it references a concept not anchored to any named alternative.

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