List Action Plan Item Assignees

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

Adds pagination behavior and mention of metadata beyond annotations. No contradictions with annotations. Could disclose more about rate limits or auth, but annotations already cover safety.

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?

Concise overall, includes actionable details. However, includes unnecessary API path and Procore API line. Front-loads purpose well.

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?

Covers pagination and required parameter but misses explaining filter parameters beyond schema. No definition of an Action Plan Item Assignee. The misnomer reduces completeness.

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 covers all parameters (100% coverage). Description only mentions project_id as required and page/per_page for pagination, adding no meaning beyond schema.

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 it lists all Action Plan Item Assignees, mentions pagination, and filtering. However, it inaccurately says 'enumerate Action Plans' and 'Returns a paginated JSON array of Action Plans', causing minor confusion.

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 context for when to use (pagination, finding IDs, filtering) but does not explicitly exclude alternatives or mention when not to use it. No differentiation from sibling tools like show_action_plan_item_assignee.

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