Show Action Plan

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

Annotations already provide read/read-only, non-destructive, idempotent hints. The description adds that it returns a JSON object and mentions the endpoint, but no additional behavioral traits. 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 and mostly front-loaded with purpose. It is concise but has minor redundancy ('Action Plans' vs 'Action Plan'). Could be slightly tighter.

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 exists, so description should compensate. It mentions 'Returns a JSON object' but does not specify fields or structure. Pagination parameters are included but may not apply to a single-resource fetch, causing some incompleteness.

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 baseline 3. The description mentions required parameters but adds no meaning beyond the schema. Optional parameters (page, per_page) are not clarified for a single-resource fetch, which might confuse.

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 'Details of a single Action Plan' and 'fetch the full details', with a specific verb and resource. It distinguishes from siblings like show_action_plan_item and list_action_plans.

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.' It includes required parameters but does not explicitly exclude alternatives (e.g., list for multiple) or mention when not to use it.

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