cat_hotel_export

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

No annotations are present, so the description carries full burden. It discloses the return format but does not mention side effects, idempotency, authentication requirements, or whether the operation is read-only. This leaves significant behavioral ambiguity.

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, clear 7-word sentence with no redundancy. It is appropriately sized for the tool's simplicity and fits the minimal structure.

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 that the tool has one optional parameter and an output schema, the description lacks context such as what the base64 string represents (e.g., entire save file), size limits, or relationship with sibling tools like import. It is minimally complete for a simple export but leaves gaps.

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 0%, and the description only implicitly mentions 'save' as the parameter. It does not explain what save_name represents, valid values, or how the default 'default' behaves. The description adds minimal semantic value over the parameter name.

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 states the verb 'Export' and the resource 'save', and specifies the output format as 'base64 string'. It is clear and distinct from siblings like import or list_saves, though it does not explicitly differentiate itself.

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 like cat_hotel_import or cat_hotel_list_saves. The description only states what the tool does, not the context or prerequisites.

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