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

Without annotations, the description carries the burden of disclosing behavior. It describes what each status means and notes that 'da_pagare' includes a payment link and 'confermato' includes the Runner's name and contact, which is useful behavioral context. However, it does not mention whether the operation is read-only, what happens if the rental is not found, or any rate limits or side effects. For a status-check tool, this is adequate but leaves gaps.

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, efficient sentence that front-loads the purpose and then lists statuses with brief parenthetical clarifications. There is no waste, and it is appropriately sized for the tool's complexity. The structure is clear and easy to parse.

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?

The tool has no output schema and no annotations, so the description must cover return values and behavior. It lists possible statuses and some associated data, which is useful, but it does not describe the return format (e.g., JSON structure) or error conditions. Given the simplicity (2 required params, no nested objects), it is mostly complete but could specify what an agent should expect in terms of output.

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 input schema already fully documents both parameters (id and codice_accesso). The description adds no additional meaning about the parameters beyond indicating that the status is for a rental requested via rentme_book_thing, which implies the access code is from that tool. Baseline 3 is appropriate when schema does the heavy lifting.

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 states the purpose: checking a rental request status, and explicitly links it to the sibling tool rentme_book_thing. It enumerates possible statuses, distinguishing it from siblings like rentme_check_task_status. However, it lacks a direct verb like 'returns' and is somewhat terse, but the intent is clear.

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 implies usage when you have a rental request created by rentme_book_thing and need its status, but does not explicitly state when to use this tool versus alternatives like rentme_check_task_status or when not to use it. It provides some context by referencing rentme_book_thing, which is helpful but not complete guidance.

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