List debugging sessions

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions sorting (most recently updated first) but does not disclose result fields, pagination behavior, default limits, whether all statuses are included by default, or if any side effects exist. The minimal disclosure falls short of what an agent needs to understand the tool's runtime behavior.

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, concise sentence that names the operation and includes one valuable detail (sort order). There is no filler or redundancy.

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?

The tool is a simple list with two optional parameters but no output schema and no annotations. The description provides only the basic listing action and sort order, omitting expected return structure, parameter semantics, and any scenarios for using filters. For an agent to invoke it correctly, more context is needed, such as what happens if no parameters are supplied or how status filtering works.

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 input schema has two parameters (limit and status) and zero schema-description coverage. The tool description makes no mention of these parameters, how to use them, or their effect on results. Since the description adds no meaning beyond the schema's bare property names and types, it fails to compensate for the lack of schema-level documentation.

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 'Lists debugging sessions, most recently updated first' clearly states the action (list) and the resource (debugging sessions), and adds the ordering detail which distinguishes it from sibling tools like debug_session_get or execution_list. This is a specific, unambiguous purpose.

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 by naming the list operation, but it does not explicitly state when to use this tool versus alternatives like debug_session_get for a single session or execution_list for executions. No exclusions or alternative guidance is provided, so it relies on the agent inferring context from the verb and sibling tool names.

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