list_murals

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

With no annotations, the description carries the burden and discloses key behavior: returned fields are stripped and default limit is 50. It does not cover edge cases like behavior when neither roomId nor workspaceId is provided, but the disclosed behaviors are significant.

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 extremely concise, two short sentences that front-load the core action and include the stripped-fields note and default limit. Every word adds value.

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?

Without an output schema, the description indicates return fields but leaves ambiguity about behavior with no filters, sorting, or error conditions. It covers the essentials but lacks completeness for a tool with optional parameters and no annotation support.

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 100%, so all parameters are documented there. The description adds minimal extra meaning beyond 'room or workspace' mapping to roomId/workspaceId, matching the baseline 3 for full schema coverage.

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 it lists murals in a room or workspace, specifying the resource and scope. It differentiates from siblings like get_mural (individual) and list_workspaces/list_rooms by mentioning stripped fields, making the tool's purpose unambiguous.

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 for lightweight listing with 'stripped to id+title+roomId' and mentions the default limit. However, it does not explicitly contrast with get_mural for full details or state when not to use it, leaving some room for inference.

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