room_local_summary

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

The description discloses behavior beyond the annotation: it explains the local cache read, offline behavior, and fallback logic. It is consistent with the readOnlyHint=true annotation, as it describes a read-only operation. No contradictions found.

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 concise (three sentences), front-loaded with the primary action, and structured clearly. Every sentence adds value, with no wasted words.

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?

Given the tool's simplicity (1 parameter) and the presence of an output schema, the description covers purpose, parameter behavior, and alternatives. It is complete and sufficient for an agent to select and invoke the tool correctly.

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?

The schema description coverage is 0%, but the description compensates by explaining the room_id parameter's effect: 'With room_id, reads that room's snapshot; without it, reads the active room or, when offline, lists all local snapshots.' This provides meaningful semantics beyond the schema.

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 clearly states the tool's purpose: 'Read a room summary from this device's local cache without contacting the relay.' It uses a specific verb (read) and resource (room summary from local cache), and distinguishes itself from siblings by mentioning room_info for live state and room_join for refreshing.

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?

The description provides explicit usage guidance: 'With room_id, reads that room's snapshot; without it, reads the active room or, when offline, lists all local snapshots.' It also tells when to use alternatives: 'Use room_info for live connection state and room_join to refresh it.'

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