get_sessions

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

The description only states it is a read operation, implying non-destructive behavior. With no annotations provided, the description carries full burden but fails to disclose any behavioral traits such as authentication requirements, error handling, or side effects.

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 concise (one short sentence), which is good for brevity but lacks necessary detail. It is not front-loaded with key information; the single sentence covers both the endpoint and optionality.

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 2 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, parameter usage combinations, error scenarios, or the nature of sessions. Essential context is missing.

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?

Schema description coverage is 0%. The description hints that session_id selects a specific session but does not clarify the purpose of the 'application' parameter. No additional meaning is added beyond the schema properties.

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 indicates a read operation on `/actuator/sessions` and distinguishes between retrieving all sessions or one session (via session_id). The verb 'Read' is appropriate, and the reference to the actuator endpoint is specific. However, it does not explain what a 'session' represents, which could be ambiguous.

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 provides no guidance on when to use this tool over alternatives (e.g., delete_session or other actuator endpoints). No prerequisites, context, or when-not-to-use instructions are given.

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