Retrieve Recycled RFI

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

Annotations provide readOnlyHint=false, but the description claims both 'Retrieve' (read) and 'Updates' (write). The endpoint is PATCH, indicating mutation, but the description does not explain what the update does (e.g., restores the RFI). No output schema is provided, and the behavior is unclear.

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 contains three sentences, but the second and third are repetitive and confusing (mentioning 'update' twice). It includes endpoint info which is not essential. Could be more concise and clearer.

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 simple tool (2 params, no output schema), the description should clarify that the tool restores an RFI from the recycle bin. It fails to do so, instead providing misleading update semantics. Siblings like recycle_rfi and list_recycled_rfis suggest this is a restore operation, but the description does not confirm it.

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 input schema has 100% coverage with descriptions for both parameters. The description redundantly lists required parameters but adds no meaning beyond the schema. Baseline 3.

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 'Retrieve a specified RFI from the Recycle Bin' which is clear, but then contradicts by saying 'Use this to update an existing RFI records' and 'Updates the specified RFI records'. This muddles the purpose, making it unclear whether the tool retrieves (reads) or updates (mutates) the RFI.

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?

No guidance is provided on when to use this tool versus alternatives like recycle_rfi, update_rfi, or show_rfi. Siblings include many RFI-related tools, but the description offers no context for selection.

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