recommend_next

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

No annotations are provided, so the description carries full transparency burden. It explains the tool recommends with reasoning and mentions an optional session_file. The output schema exists but is not shown; the description does not cover output format, but the example hints at a recommendation with reasons. Overall, it is sufficiently transparent for a recommendation tool.

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 two sentences plus an example, front-loaded with purpose, and contains no unnecessary words. It is efficiently structured and easy to parse.

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 the tool's recommendation nature and the presence of an output schema (which handles return value documentation), the description covers all essential input semantics and usage context with an example. It is fully complete for agent decision-making and invocation.

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%, so the description must compensate. It explains current_stack as 'list of server names', new_context as 'development context', and session_file as 'optional path to session notes file whose content is appended to new_context'. This adds meaningful context beyond the schema. A slight improvement could clarify the format of current_stack entries.

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 the tool recommends what to add next given current stack and new context, with an example. It distinguishes from sibling tools (explain_why, recommend_for_goal, recommend_for_project) by focusing on 'next additions' in a mid-project advisor role.

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 implies usage as a 'mid-project advisor' and provides an example, giving clear context. However, it does not explicitly state when not to use this tool or contrast with alternatives, slightly limiting guidance.

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