Retrieve Recycled Witness Statement

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

Annotations are provided but the description adds confusion by mixing 'retrieves' and 'updates'. It does not clearly disclose that this is a restore operation (PATCH /restore). The description mentions the endpoint path indicating restore, but the contradictory language undermines transparency.

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 four sentences, but includes redundant or irrelevant information (e.g., Procore API version and endpoint path) and contradictory statements. It could be more concise and focused.

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 exists, but the description only vaguely says 'returns the modified object on success'. It does not specify what fields the response contains, prerequisites (e.g., witness statement must be in recycle bin), or error conditions. Incomplete for a restore operation.

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% with clear parameter descriptions. The description only restates that project_id and id are required, which duplicates schema info. It does not add additional meaning such as how these parameters are used in the restore context.

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 contradicts itself: 'Retrieves a specific Recycled Witness Statement' suggests a GET operation, but then says 'Use this to update an existing Incidents' and 'Updates the specified Incidents'. The actual HTTP method is PATCH, indicating an update/restore, not a simple retrieval. The purpose is misleading and unclear.

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. Sibling tools like show_recycled_witness_statement (GET) and update_witness_statement exist, but the description does not differentiate this restore operation from them. No when-not-to-use or exclusions are provided.

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