Retrieve Recycled Observation

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

Annotations indicate readOnlyHint: false and destructiveHint: false, but description says it updates. No explanation of what the restore operation entails (e.g., status change, moving back to active). Insufficient disclosure of side effects.

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?

Description is four sentences but contains contradictory statements ('Retrieves' vs 'Updates'). Includes endpoint info which is unnecessary. Not well-organized or succinct.

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?

No output schema and description only says 'returns the modified object' without details. Missing error conditions or prerequisites. Given the tool's complexity (restore from recycle bin), more context is needed.

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?

Input schema has 100% coverage with descriptions for both parameters. The description redundantly states required parameters but adds no extra meaning beyond the schema.

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 says both 'Retrieves' and 'Updates', which is contradictory. The tool name suggests reading, but the endpoint is a PATCH to restore, implying mutation. This confuses the agent about the actual purpose.

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 on when to use this tool versus alternatives like 'restore_recycled_action_plan' or other restore tools. Does not specify prerequisites (e.g., observation must be in recycle bin) or when not to use.

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