recommend_session_for_today

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

No annotations are provided, so the description carries the full burden. It indicates the tool is read-only (returns recommendation), but does not disclose side effects, authentication needs, or rate limits. The mention of 'deload triggered' gives a hint of logic but not sufficient behavioral detail.

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 a single, compact sentence of about 20 words. It front-loads the purpose and context, and includes a concrete example ('deload triggered'). No wasted or redundant words.

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?

Given 4 parameters, no output schema, and no annotations, the description is too brief. It does not specify the return structure or format of the rationale. For a tool that likely returns a complex session recommendation, this leaves significant ambiguity.

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 description coverage is 0% (no descriptions on individual parameters). The description only names the parameters generically: 'template, current week, fatigue state, and last session'. It does not clarify the structure of 'fatigue' (a loosely typed object) or expected format of 'last_session'. This adds minimal value beyond the schema's property names.

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 it returns a recommended session with rationale, using inputs like template, week, fatigue, and last session. This distinguishes it from siblings like 'calculate_fatigue_score' and 'get_template_plan', though 'suggest_session_modification' could overlap. The example 'deload triggered' adds specificity.

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 this tool versus alternatives. The description implies it is for generating a recommendation when you have template, week, fatigue, and last session, but does not mention prerequisites, when not to use it, or how it relates to siblings like 'calculate_fatigue_score' or 'suggest_session_modification'.

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