whoami

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

Without annotations, the description does not explicitly state that the tool is read-only or idempotent, but it does disclose that the OAuth bearer is never returned, addressing a potential security concern. More behavioral context (e.g., no side effects) would improve this score.

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?

Two sentences, no filler, essential information front-loaded. Every sentence adds value.

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?

For a simple, parameterless tool, the description fully covers the return values and includes a security note. No output schema is present, but the description sufficiently informs the agent of what to expect.

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?

With zero parameters, schema description coverage is 100%. The description adds value by listing the output fields, which are not captured in the schema. Per guidelines, 0 params warrants a baseline of 4.

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 'describe' and the resource 'currently logged-in servonaut.dev session', and lists specific return fields (email, plan, API base URL, token expiry). It distinguishes itself from sibling tools as the only tool providing session information.

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 explicit guidance on when to use vs alternatives, but the purpose is clear enough for an agent to infer its use for checking authentication status. However, no exclusions or alternative suggestions are given.

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