get_me

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

With no annotations, the description carries the full burden. It discloses one key behavioral constraint: the need for prior login. However, it doesn't mention side effects (likely none), whether the session is read-only, or what happens if called without login (error vs. null). This adds some context but not comprehensive behavioral coverage.

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, concise, front-loaded sentence. It states the tool's action and the prerequisite without any filler. Both pieces of information are essential, and there is zero redundancy.

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 it is a simple getter with no parameters and no output schema, the description is mostly complete. It defines the operation and a critical prerequisite. It doesn't describe what 'session information' includes, but for a trivial tool, this is acceptable. A minor gap is not detailing the failure mode when not logged in.

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 tool has zero parameters, so the schema fully covers the parameter space. Per the rubric, a baseline of 4 is appropriate since there are no parameters to describe. The description adds no parameter-specific detail, but none is needed.

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's function: 'Get the current authenticated user's session information.' The verb 'Get' and the specific resource 'current authenticated user's session information' precisely define what it does, and it is distinct from sibling tools like list_personas or get_persona.

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 explicitly states a prerequisite: 'Requires prior login via the login tool,' which tells the agent when this tool is appropriate. It doesn't explicitly exclude alternative tools, but the purpose is unique enough that little else is needed. If the user hasn't logged in, this tool should not be used, which is implied.

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