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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. "Reject" implies a state-changing, likely irreversible action, but the description says nothing about permissions, whether the proposal can be re-opened, whether a rejection reason is recorded, or what the response contains.

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?

It is a single front-loaded sentence with zero filler, so nothing is wasted. However, it is a bare fragment with no structure beyond the verb phrase, leaving no room for the scoping or state details an agent needs.

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?

This is a state-changing tool with no annotations, no output schema, and 0% parameter coverage, yet the description is one five-word sentence. It omits irreversibility, permissions, the optional room parameter, and outcome behavior — an agent could easily call it wrongly or with unintended 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 0%, so the description must compensate and does not. "By id" loosely maps to the required 'proposal' parameter (pattern ^p_[a-z0-9]+$), but the optional 'room' parameter, its regex-constrained format, and whether it defaults to the current room are entirely undocumented.

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 states a specific verb and resource: "Reject a proposal by id." An agent can tell this mutates a proposal's state rather than accepting, editing, or listing one. It stops short of explicitly differentiating from the obvious counterpart (world_accept) or describing what rejection entails.

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?

There is no when-to-use guidance, no mention of when rejection is appropriate versus world_accept or world_edit, and no stated prerequisites such as required role or proposal state. The agent must infer all routing decisions from the name alone.

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