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

Absent annotations, the description conveys key behavioral traits: it reads from session state without invoking an API. However, it does not specify what happens on invalid session_token or whether the tool modifies state.

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, well-structured sentence that communicates the core purpose. However, it sacrifices parameter details, which might be necessary for completeness.

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 3 parameters, no schema descriptions, and no output schema, the description is insufficient. It omits parameter roles, output format, and potential side effects, leaving the agent to guess.

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 description adds no meaning to the three parameters (os, message, session_token). With 0% schema description coverage, this is a critical gap—the agent has no guidance on what each parameter does.

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 answers from session state without invoking a model API, distinguishing it from API-calling tools. However, it could be more explicit about the specific resource ('ODEI Connect session state').

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 a model API call is undesired, but lacks explicit guidance on when to use this tool versus alternatives like odei_connect_plan or wm_recall.

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