Show Recycled Action Plan Item Assignee

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, effectively communicating the safe read behavior. The description adds endpoint and API category details but no significant behavioral traits beyond 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 is relatively short but contains confusion (mixing 'Action Plans' with item assignee) and slight redundancy ('fetch the full details' and 'Returns a JSON object'). Every sentence should be precise; this one isn't.

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, yet the description only vaguely says 'Returns a JSON object describing the requested Action Plans' (likely incorrect). It fails to explain pagination parameters (page, per_page) or the expected response structure, leaving gaps for an agent.

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 covers 100% of parameters with descriptions. The description reiterates required parameters and provides endpoint context, but adds minimal semantic value beyond what the schema already offers.

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 'Details of a single Recycled Action Plan Item Assignee' but then says 'fetch the full details of a specific Action Plans by its identifier', which is contradictory and misidentifies the resource. This confusion impairs clarity for an AI agent selecting the tool.

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?

Only required parameters (project_id, id) are mentioned. No guidance is given on when to use this tool versus sibling tools like show_recycled_action_plan or show_recycled_action_plan_item, leaving the agent without context for differentiation.

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