get_room_info

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

The description indicates a read operation via 'Get', and lists the returned data. With no annotations, it carries the full burden; 'Get' implies no side effects, but could explicitly state it doesn't modify anything. However, the verb is sufficiently clear.

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 a single sentence that front-loads the purpose and efficiently lists the return categories. Every part is necessary.

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 no output schema, the description adequately covers what the tool returns. However, it does not mention prerequisites (e.g., room must exist) or error conditions, but for a straightforward read tool this is acceptable.

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 100%, and both parameters have descriptions in the schema. The description adds no additional semantic value beyond the schema, so baseline score of 3 is appropriate.

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 verb 'Get detailed info' and specifies the resource type 'existing room'. It enumerates the specific information returned (dimensions, persistence, layers, instances with positions), distinguishing it from sibling tools like get_note_info or get_object_info.

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 implies usage when detailed room info is needed, but does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusions or context for when not to use it.

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