mempalace_get_taxonomy

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

With no annotations, the description must disclose behavioral traits. It states the output structure but omits whether the operation is read-only, destructive, or if it requires authentication. The phrase 'full taxonomy' implies a composite view but lacks details on side effects or error behavior.

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 (one short phrase). It is front-loaded with the key concept. However, it could be slightly more structured (e.g., listing return format) without adding much length. Still, it is efficient for a zero-parameter tool.

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 parameters and no output schema, the description provides the essential purpose but leaves ambiguity about the exact return format (e.g., whether 'drawer count' is per room or a total). The hierarchical notation is clear but could be more explicit. For a simple retrieval tool, this is adequate but not comprehensive.

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 input schema has zero parameters, so schema coverage is 100%. The description adds meaning by explaining the output hierarchy (wing → room → drawer count), which is not apparent from the empty schema. No parameter details are needed, but the description still adds value 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 indicates the tool retrieves a full taxonomy hierarchy (wing → room → drawer count). The verb 'get' is implicit, and the resource 'taxonomy' is defined. However, it does not explicitly distinguish from sibling tools like mempalace_list_wings or mempalace_list_rooms, which offer more granular views.

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 provided on when to use this tool versus alternatives such as mempalace_list_wings or mempalace_get_drawer. The description does not mention prerequisites, performance implications, or cases where a more specific list tool would be preferable.

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