Taxpayer session status

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

No annotations are provided, so the description carries the full burden. It does add useful behavioral context by specifying the session check is in 'this server process,' and 'reports' suggests a read-only operation. However, it does not disclose potential edge cases like session expiration behavior, whether the check has side effects, or what happens if no session exists.

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?

A single, front-loaded sentence with no filler. Every word contributes meaning: 'Reports,' 'active,' 'taxpayer session,' and 'in this server process' all carry necessary information.

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 zero-parameter, no-output-schema tool, the description is nearly sufficient. It tells the agent what is being checked and the scope, and 'reports whether' naturally implies a boolean result. A minor gap is not explicitly stating the return format or any prerequisites, but the tool's simplicity keeps this from being a major omission.

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 is trivially complete. The baseline for zero-parameter tools is 4, and the description adds no irrelevant parameter information. No parameter semantics are missing.

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 uses a specific verb ('Reports') and a clear resource ('whether an active taxpayer session exists') scoped to 'this server process.' It is distinct from sibling tools like taxpayer_generate_otp and verify_gstin, which handle session creation or GSTIN lookups rather than session status.

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: an agent would call this to determine if an authenticated session exists in the current server process before proceeding with session-dependent operations. However, it does not explicitly state when to use it, when not to use it, or mention any alternatives, so the guidance is only implied.

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