Get advisor session state

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so safety is covered. The description contributes the shape of what is returned (goal, constraints, decisions, open questions, call count, recent consults), but says nothing about how many "recent consults" are included, behavior for an unknown/expired session_id, or whether state persists across resets.

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?

One sentence, front-loaded with the verb, with the returned fields enumerated as a compact list. No filler or repetition of the title.

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 correctly takes on the job of enumerating return values, which it does thoroughly. The remaining gap is operational: how to obtain a valid session_id and what an unknown id yields.

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 single session_id parameter has 0% schema description coverage, so the description carries the burden of explaining it — yet it only restates "for a session_id" without saying where the id comes from (returned by consult_advisor? update_advisor_session?) or its format. It adds no meaning beyond the schema's type and length bounds.

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?

States a specific verb ("Return") and resource (accumulated session state for a session_id) and enumerates the exact fields returned, so an agent can tell it apart from consult_advisor, update_advisor_session, and reset_advisor_session. It stops short of explicitly naming those siblings, but the read-only state-recall framing is unmistakable.

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?

There is no explicit when-to-use, when-not-to-use, or alternative named. Usage is only implied by the field list (you call it to recover prior context before consulting), leaving the agent to infer that this is the recall step in the advisor workflow.

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