get_template_plan

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

Explicitly states 'Pure function: same input returns same output,' which discloses deterministic behavior and lack of side effects. This compensates for missing annotations, though error handling or access constraints are not mentioned.

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?

Two sentences, zero waste. First sentence states purpose, second adds behavioral and output details. Information is front-loaded and every word earns its place.

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?

Describes output structure (list of sessions with sets, reps, etc.) despite no output schema. Covers key inputs and behavior. Missing edge cases like missing template or invalid week, but sufficient for a simple get operation.

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 provides 100% coverage with clear descriptions (e.g., 'Template ID from list_training_templates'). Description adds no extra meaning beyond what schema already conveys, so baseline 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?

Description clearly states 'Get a specific week's sessions from a template.' It uses a specific verb and resource, distinguishing it from sibling tools like list_training_templates (list) and others that modify or analyze.

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?

No explicit guidance on when to use vs alternatives. The 'Pure function' note hints at idempotency but doesn't define usage context or prerequisites. Implied usage is retrieving planned sessions.

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