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

No annotations are provided, so the description carries the full behavioral burden. It does convey that this is a read-only status check and lists the expected status values, which is useful. However, it does not disclose behavior for missing/unknown tasks, whether both id and riferimento_ai can be supplied together, or any error/return conventions.

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?

A single, well-structured sentence front-loads the verb and resource, then adds statuses and lookup methods. There is no filler or redundant repetition of the tool 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?

Given the low complexity of the tool—two optional parameters, no output schema, no nested objects—the description covers the core behavior, the possible status values, and both lookup keys. It is slightly incomplete in not stating what happens when no task matches or whether the result is just the status string, but it is adequate for selection and basic invocation.

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 adds value by stating that the tool searches 'per id interno o per riferimento_ai', which communicates that the two parameters are alternative lookup keys and that riferimento_ai was provided at creation time. This relationship is not explicit in the schema alone.

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 uses a specific verb and resource: 'Controlla lo stato di avanzamento di un task' and enumerates the possible statuses. It also clarifies the two lookup modes, making it clearly distinct from the sibling rentme_create_task, whose purpose is creation.

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 makes the use case clear: checking the status of an already-created Rentme task via either internal id or external riferimento_ai. It does not explicitly say 'use this instead of rentme_create_task', but the contrast between checking and creating is implied enough given the single sibling.

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