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

Goes well beyond the annotations by disclosing that the tool only mints a link (the actual import happens on the user's upload), that the link is single-use and expires in an hour, that results are private cookbooks named after the file with photos preserved, that Paprika stars map to my_rating, that nutrition is estimated afterwards, that limits are 100 MB / 3000 recipes, and that duplicates are skipped on re-upload. These are exactly the operational facts the readOnly/destructive hints cannot convey.

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?

Front-loaded with the action and the link mechanism, then limits, then triggers, then follow-up — a sensible order. It is dense and long-jammed into a few run-on sentences (limits, dedup, and expiry all in one breath), but nearly every clause carries information an agent would otherwise guess wrong.

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?

Despite zero parameters, the description covers the full interaction: supported formats, what gets created, what the user must do with the link, size caps, dedup behavior, and the natural next step. With an output schema present it rightly does not describe the response payload.

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 tool takes no parameters and the description makes the interaction model clear — the file is dropped via the returned link rather than passed as an argument, so there is nothing for an agent to supply. No further parameter detail is needed.

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?

Opens with a specific verb+resource: returns a one-time upload link for recipe-app exports, naming the exact file formats (Paprika, Mela, Crouton, schema.org zip). It also explicitly distinguishes itself from upload_recipe, so an agent can tell the bulk and single paths apart without opening any schema.

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?

Gives concrete trigger phrases ("import my Paprika recipes", "bring my recipe collection over") plus a quantitative rule ("more than a few recipes to add at once") and names the competing tool: "upload_recipe stays the tool for a single recipe." It even prescribes the post-import follow-up (list_saved with the new cookbook).

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