Get the AI planner templates

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

Annotations already mark this as read-only and non-destructive. The description adds useful behavioral context: costs must not be guessed, plan generation is disabled without PLANVORTEX_MCP_ALLOW_AI=1, and missing create_ai_plan is explained. There is no contradiction with 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 longer than average but the content is mostly high-value: template names, cost warnings, and environment requirements. It is front-loaded with the core purpose, though some phrasing could be tightened without losing meaning.

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?

With no output schema, the description adequately conveys the returned template names, the key cost caveat, and the environment dependency. Exact response formatting is not specified, but the tool itself provides those details at runtime.

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?

This tool has zero parameters, so the description carries no parameter burden. A baseline of 4 is appropriate since the schema requires no additional explanation.

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 defines what the tool returns: the AI plan templates and their credit costs. It names all five template types with enough detail to distinguish this from get_ai_plan and list_ai_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?

It gives an explicit when-to-use instruction ('Read this before proposing a plan') and explains the condition under which AI plan creation is available. It does not name alternative tools directly, but the context is clear enough for an agent to use it correctly.

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