session_suggest_formulas

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the return type and purpose, but omits side effects, authentication needs, or prerequisites (e.g., a session goal must be set). Since this is a read-only suggestion tool, the lack of destructive behavior disclosure is acceptable, but other details are missing.

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 very concise: one main sentence, plus Args and Returns sections with clear labeling. Every part serves a purpose, and key information is front-loaded.

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?

The tool is simple with one parameter and an output schema, so the description covers the basic purpose. However, it lacks context about prerequisites (e.g., an active session with a goal) and does not describe the rationale format in the output. Additional details would improve completeness.

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?

The input schema has 0% description coverage, so the description compensates by explaining that top_k is the 'Maximum number of suggestions.' This adds basic meaning beyond the schema, but does not elaborate on the default value or valid range.

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 that the tool suggests formulas to help achieve the current session goal, with a specific verb 'suggest' and resource 'formulas'. It distinguishes from sibling tools like formula_search (which searches by query) and session_set_goal (which sets the goal).

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 when the agent needs suggestions related to the session goal, but it does not explicitly state when to use this tool versus alternatives like formula_search or tool_recommend. No exclusions or conditions are provided.

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