Show Recycled Action Plan Template Items

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

The description adds value beyond annotations by explaining error behavior ('401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve') and the read-only nature ('changes nothing in Procore'), which aligns with the annotations. This is useful operational context not present in the structured data.

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 a single dense paragraph that includes all necessary information, but it repeats the return behavior and required parameters already evident from the schema. It could be more concise and structured, but it remains readable and front-loaded.

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 absence of an output schema, the description reasonably states it returns 'a single JSON object' and covers failure modes and endpoint details. For a simple read tool, this is adequately complete, though it could be slightly more specific about return fields.

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 schema already provides 100% coverage for both parameters, but the description adds meaning: company_id defaults to the procore_set_config value, and id must reference an existing parent record resolved via the list tool. This goes beyond the raw schema descriptions.

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 clearly states 'Returns a Specific Recycled Action Plan Template Item for a given company,' using a specific verb and resource. It also distinguishes itself from the list tool by saying 'Use this when you already know which recycled action plan template item you want and need its full field set.'

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?

Provides clear context for when to use the tool ('when you already know which...'), and explicitly instructs to resolve the id with the matching list tool first. It lacks an explicit 'when not to use' but the guidance is sufficient.

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