List Recycled Action Plan Items

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Returns a paginated JSON array of Action Plans. Use page and per_page to control pagination; the response includes pagination metadata.' It also mentions the Procore API endpoint, providing useful context beyond 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 is concise—four sentences addressing purpose, usage, pagination, and endpoint info. Every sentence adds value without redundancy. Well-structured 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?

The description covers purpose, usage, pagination behavior, and required parameter. It mentions the return type (JSON array) and pagination metadata. However, it does not describe the structure of the returned items or explain 'Recycled Action Plan Items' in more detail. Given no output schema and 9 parameters, it is adequate but not fully comprehensive.

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%, so the schema fully documents all 9 parameters. The description only highlights 'Required parameters: project_id.' It adds no further detail per parameter, which is adequate given the schema's completeness. Score at baseline 3.

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 all Recycled Action Plan Items for a given Project.' It identifies the resource and action. However, it does not explicitly differentiate from sibling tools like 'list_recycled_action_plan' or 'list_recycled_action_plan_item_assignees', though the resource name is specific.

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?

The description advises 'Use this to enumerate Action Plans when you need a paginated overview, to find IDs, or to filter by query parameters.' This provides concrete use cases but lacks explicit guidance on when not to use it or alternatives among siblings.

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