session_status

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

The description adds a fact the annotations do not carry: no authentication is required to call it, and it never mutates state. The read-only/no-change claim partially restates readOnlyHint and destructiveHint=false, but the 'does not require login' disclosure is genuinely new and useful for an agent deciding call order.

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?

Three short sentences, front-loaded with the returned fields, then usage triggers, then the safety/auth caveat. Every sentence carries information and none repeats the title.

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?

No output schema exists, yet the description enumerates what is reported, which is exactly what the agent needs. The only gap is the undeclared `probe` parameter, which is not reflected in the schema and would need to be resolved elsewhere.

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 the baseline is 4, but the description references a `probe: true` argument while the input schema declares an empty properties object. An agent following the description would attempt a parameter the schema does not expose, creating real ambiguity that offsets the otherwise clean no-param case.

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?

States a specific verb (report) and enumerated resource elements: active session, registration number, credential configuration, and optional validity probe. It is immediately distinguishable from siblings like logout and login, which act on the session rather than report on it.

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?

Gives explicit triggers: 'Call this before logging in if unsure' and 'when a data tool returns NOT_AUTHENTICATED.' It names the condition and the situation, leaving nothing to inference about when to reach for this instead of login.

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