Retrieve Recycled Incident

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

Annotations indicate readOnlyHint=false, consistent with a mutation. The description discloses it updates incidents and returns the modified object. However, the term 'retrieve' is misleading, and the description does not clarify that it restores the incident from the recycle bin (as the endpoint suggests). Behavioral disclosure is adequate but lacks nuance.

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 is relatively short but includes contradictory statements (retrieve vs update) and is not well-structured. The inclusion of Procore API details and endpoint URL is useful, but the clarity is compromised.

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 tool's simplicity (2 required params, no output schema), the description should clearly explain the operation (restoration) and return value. It mentions 'returns the modified object' but does not specify that the incident is restored from the recycle bin. The lack of clarity on the outcome leaves the agent uninformed.

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 2 parameters with 100% description coverage. The description redundantly lists 'Required parameters: project_id, id' without adding meaning beyond what the schema provides. No new semantics are introduced.

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 the specified Incident from Recycle Bin' but then immediately contradicts by saying 'Use this to update an existing Incidents' and 'Updates the specified Incidents'. The tool name suggests retrieval, yet the description describes an update/restore operation, making the purpose vague and confusing.

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?

There is no explicit guidance on when to use this tool versus alternatives like restore functions. It lists required parameters but does not provide context on prerequisites, who should use it, or when it is appropriate to call.

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