Show Action Plan Item Assignee

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the agent knows this is a safe read operation. The description adds the API endpoint and required parameters, but does not disclose behavioral traits beyond what annotations provide. No contradictions.

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 4 sentences but includes redundant mentions of 'Action Plans' and an error. It could be more concise and front-loaded. The API endpoint information is useful but not critical.

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?

For a simple retrieval tool with annotations and schema, the description provides the endpoint and required parameters. However, it does not explain pagination parameters (page, per_page) which are in the schema, and the error about Action Plans reduces completeness. No output schema, but description doesn't elaborate on return structure. Adequate but not excellent.

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 100% coverage with descriptions for all properties. The description only repeats 'Required parameters: project_id, id' which adds no new meaning beyond the schema. Baseline score of 3 is appropriate.

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 Action Plan Item Assignee' but then incorrectly says 'fetch the full details of a specific Action Plans' and 'Returns a JSON object describing the requested Action Plans.' This inconsistency between the tool name and description weakens purpose clarity, as it may confuse the agent about what exactly is being retrieved.

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 says 'Use this to fetch the full details of a specific Action Plans by its identifier' but provides no differentiation from sibling tools like 'show_action_plan_item' or 'list_action_plan_item_assignees'. It lacks guidance on when to use this tool versus alternatives.

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