sys_max_session

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

With no annotations provided, the description carries the behavioral burden. It does disclose the key trait — read-only — which signals a non-mutating operation. However, it adds no context about output, error behavior, or what 'maximum session' configuration actually returns, leaving the agent to infer the rest.

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 efficient sentence with the purpose front-loaded. Appropriate length for a 0-param read-only tool; nothing is wasted, though the ambiguity of 'maximum session' means brevity comes at the cost of precision.

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 0-param read-only tool, the description is mostly complete — it needs no parameter documentation. However, without an output schema and with the ambiguous 'maximum session' phrasing, an agent cannot fully predict what data will be returned or what the configuration refers to.

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 description has nothing to clarify beyond the schema. Per baseline, 0-param tools earn a 4; the read-only qualifier adds marginal semantic value about the operation, not parameters.

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 names a resource ('session configuration') and discloses a read-only nature, which partially distinguishes it from siblings like show_session and ip_session. However, 'maximum session' is ambiguous — it could mean max concurrent sessions, max session timeout, or another dimension — so the purpose is stated but not precise.

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 guidance is given on when to use this tool versus alternatives. Among many session-related siblings (show_session, ip_session, sys_* tools), there is no differentiation, no exclusions, and no mention of what this tool offers that others don't.

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