mempalace_list_drawers

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

The description mentions pagination (limit, offset) and optional filters, but does not state if the tool is read-only, order of results, or any constraints like rate limits or authentication requirements. Since no annotations are provided, more behavioral detail would be expected.

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 concise sentence that front-loads the main action and then provides key details. Every word earns its place.

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?

While the description lists return fields (IDs, wings, rooms, content previews), it does not mention pagination metadata like total count or next page token, which is expected for a paginated list tool. The absence of an output schema makes this description somewhat incomplete.

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%, so baseline is 3. The description adds no new meaning beyond the schema; it simply restates that wing and room are optional filters and mentions pagination generically.

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 that the tool lists drawers with pagination and optional filtering by wing and room. It returns IDs, wings, rooms, and content previews, but does not explicitly differentiate from siblings like mempalace_get_drawer or mempalace_search.

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 on when to use this tool versus alternatives. There is no mention of when not to use it or which sibling tool might be more appropriate for specific queries.

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