session_status

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

Annotations provide readOnlyHint=true, and the description adds detailed behavioral context about what information is returned (token lifecycle, credential storage status, etc.), fully explaining the non-destructive read operation.

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 well-structured with a summary line and bullet points, but the bullet points listing each field are somewhat redundant given the output schema exists. Still efficient and front-loaded.

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 zero parameters, the description comprehensively covers the tool's purpose, output fields, and usage context. The presence of an output schema does not reduce the need for description, and the description adds value beyond schema field names by explaining semantics like 'refresh_recommended: Whether proactive refresh is advised (< 4 hours remaining)'.

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?

No parameters exist (schema coverage 100%), so the description naturally covers all semantics by explaining the output. No additional parameter meaning 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 gets current session status, listing all relevant fields (authenticated, needs_refresh, etc.) and distinguishing it from sibling tools like session_refresh and session_clear.

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?

Explicit guidance: 'Use this to check session health before operations or to decide when to proactively refresh.' This tells the agent when to use it and implies contexts like post-authentication or before expensive operations.

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