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

Annotations already establish that this is not read-only, not open-world, and not destructive, but the description adds important behavioral context: it is a two-phase operation requiring a preview and owner approval. It also discloses the owner sign-in requirement. It does not discuss idempotency, what happens to rows not confirmed, or detailed side effects beyond loading into the hotel.

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 three short sentences and front-loads the core action before explaining the two-step workflow and the sign-in requirement. Every sentence adds useful information with no filler.

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?

For a one-parameter mutation tool with no output schema, the description covers the essential workflow, approval step, and authentication prerequisite. It does not fully explain what the preview returns, how decisions are represented, or error behavior, but it is complete enough for an agent to use the tool correctly in normal operation.

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 schema already documents the single confirm parameter, but the description adds substantial meaning: omitting confirm produces a preview of rows needing a decision, while confirm true loads them. This explains the parameter's role in the workflow beyond the schema's brief 'true to load' text.

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 a specific verb and resource: it loads stays read from reports into the hotel. It also distinguishes the action from a simple read by describing the preview-then-confirm workflow. It does not explicitly name sibling tools such as stays or upload_report, so it stops short of full sibling differentiation.

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 gives clear usage guidance: call first without confirm to preview rows, show them to the owner, then call with confirm true. It also states the prerequisite that the owner must be signed in. It does not describe when not to use this tool or compare it directly with sibling alternatives.

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