perspective_list_sessions

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

The description only indicates 'Read-only', implying no side effects, but fails to disclose any other behavioral traits such as result format, pagination, or authentication requirements. With no annotations, the description should provide more context.

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 extremely brief (one short sentence), but it fails to be informative. Every word should add value, but here it only states obvious facts. It is concise but not effectively structured.

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 the tool has no parameters and an output schema exists, the description should clarify the tool's purpose and what the output represents. It only says 'Read-only, REST plane' which is insufficient for complete understanding.

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?

There are no parameters, and schema coverage is 100%. The description does not add parameter-specific information, but this is acceptable as baseline for zero-parameter tools. The description could still add context about return values but is not required.

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 'Read-only, REST plane (Perspective module API)' is vague and does not clearly state that the tool lists sessions. It avoids specifying the verb and resource, making it indistinguishable from other perspective tools. The name 'list_sessions' does the work, not the description.

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 provided on when to use this tool versus alternatives like 'perspective_list_views' or other session-related tools. The description offers no context for tool selection.

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