Retrieve Recycled Near Miss

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

Annotations indicate readOnlyHint=false, but the description uses the word 'Retrieves', implying a read operation. It also mentions updating, but does not disclose that this is a restore operation (the endpoint is PATCH .../restore). The description contradicts both the tool name and the annotations.

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 has multiple sentences but includes redundant information (e.g., Procore API section, endpoint path). It could be more concise and clear, but is not overly long. Some sentences are confusing and could be removed.

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 is provided, and the description does not explain the return structure beyond 'returns the modified object'. More critically, it fails to clarify the tool's actual behavior (restore vs. update vs. retrieve), leaving the agent with incomplete context for correct 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%, with parameter descriptions already present. The description only repeats minimal info ('Required parameters: project_id, id') and adds no additional meaning beyond what the schema provides.

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 'Retrieves a specific Recycled Near Miss from the recycle bin' but then contradicts by saying 'Use this to update an existing Incidents'. It also mentions 'Updates the specified Incidents' which is inconsistent with the tool name and title. The purpose is vague and misleading.

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. There are many sibling tools for recycled items (e.g., retrieve_recycled_incident, retrieve_recycled_injury), but no differentiation 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.