get_session_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the conceptual purpose and does not mention authentication requirements, side effects, read-only status, or output behavior. The verb 'get' weakly implies a read operation, but this is not explicit or sufficient.

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 one short sentence with the core action front-loaded and no redundant words. It is compact, though it is also minimal enough that it reads almost like an expansion of the tool name rather than a fuller definition.

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 six parameters and no annotations or output schema, the description is too sparse to be contextually complete. It omits authentication context, what the returned session data looks like, and when this tool should be chosen over closely related get_* tools.

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 100%, so the schema already documents all six parameters. The description adds no parameter-level meaning beyond what the schema provides, such as how 'keys' relates to session data or how token/password authentication is intended to work.

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 verb 'Get' and the resource 'session data for a request', which is a specific action. However, it does not elaborate on what session data consists of or how it differs from sibling tools like get_request or get_auth_user, so differentiation is left mostly to inference.

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 when-to-use or when-not-to-use guidance is provided, and no alternative tools are mentioned. An agent gets no help deciding between this and the many similar get_* tools beyond the one-line resource statement.

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