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

Annotations only declare the readOnly/destructive/openWorld triple; the description adds substantially more: a 4 MB limit, accepted formats, an owner-authentication requirement, the side effects (creating rooms, room types, rates, taxes, stays), and a return signal ('Returns what was found'). That is meaningful behavioral disclosure beyond structured fields.

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?

One dense sentence plus two short ones, with the send/scope constraint front-loaded and the side effects and prerequisite trailing. There is no filler or restatement of the name.

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 two-parameter ingest tool with no output schema, the description covers formats, size, auth, and what the server does with the content, which is close to sufficient. It omits edge behavior such as duplicate re-uploads, parse failures, or whether an upload can be undone.

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 the baseline is 3; the description earns one step above by constraining the content parameter to CSV, tab-separated or plain text under 4 MB, which is not stated in the schema. The filename parameter gains nothing beyond the schema's own example ('bookings.csv').

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 ('Sends one report's content as text') and immediately identifies what the tool produces ('sets up what it can (rooms, room types, rates, taxes, stays)'). It is clearly distinguishable from siblings like load_stays or submit_facts, though it never names an alternative explicitly.

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?

It gives real usage direction: 'read a PDF or spreadsheet first and send its rows', plus the accepted text formats and size ceiling, and the prerequisite 'Needs the owner's sign-in.' It stops short of stating when not to use this tool or which sibling to prefer for adjacent tasks.

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