phantom_sessions

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the tool lists sessions, but does not indicate whether it is read-only, requires authentication, has rate limits, or whether it returns all sessions at once (e.g., pagination). Lack of info on side effects or safety.

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 a single sentence that front-loads the action and key details. Every word is necessary and contributes to understanding the tool's purpose. No wasted text.

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 list tool, the description is nearly complete. It specifies what is listed (sealed and active sessions) and the output fields (IDs, descriptions, timestamps). It lacks mention of ordering, pagination, or any limits, but given simplicity, it is adequate.

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 no parameters, and schema description coverage is 100%. The baseline for zero parameters is 4. The description does not need to add parameter details, but it could mention that no parameters are required. It correctly omits param info.

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 it lists all Phantom sessions (both sealed and active) and specifies the returned fields (IDs, descriptions, timestamps). It uses a specific verb and resource, and distinguishes from sibling tools like phantom_seal or phantom_audit.

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 when one needs to list sessions, but provides no explicit guidance on when to use this tool versus alternatives (e.g., phantom_status, phantom_audit). There are no when-not conditions or comparisons.

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