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

With no annotations, the description must disclose behavior itself. It adds a useful behavioral detail—'Reading inside a room needs a pass'—and hints at the return shape via field names. But it does not state whether the tool is read-only, whether listing requires authentication, or what the actual output structure is.

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 two short sentences with no filler, and the access requirement is worth stating. However, the opening fragment 'The rooms:' is awkward and would read better as an explicit action statement.

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 tool with no parameters and no output schema, the description still leaves the core action ambiguous. An agent cannot confidently know whether calling this tool returns a list, opens a room, or performs some other operation, which is a critical gap for invocation.

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 are zero parameters, so the schema requires no documentation. The description's mention of room attributes (slug, name, description, tier) partially compensates for the missing output schema by hinting at the expected result shape.

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 identifies the resource ('rooms') and its fields (slug, name, description, tier), so an agent can infer the tool relates to boards. However, it lacks an explicit verb: it never states whether the tool lists, creates, or otherwise operates on rooms, making the purpose somewhat vague.

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 guidance is given about when to use this tool versus alternatives like 'board', 'feed', or 'search'. There are no conditions, examples, or exclusions, so the agent must guess which tool fits a given intent.

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