derivation_list_sessions

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

With no annotations provided, the description carries the burden of disclosing behavior. It only states the return value, which is already covered by the output schema. It does not explicitly mention that the operation is read-only, nor does it discuss ordering, pagination, or potential side effects, so transparency is limited.

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, containing only a purpose statement and a Returns note. No redundant words or unnecessary details. The structure is acceptable for such a simple tool.

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 description is sufficient for a basic list operation, but it lacks context about what constitutes a 'derivation session' and whether pagination or ordering applies. The output schema likely covers the return structure, so the lack is more about usage and behavioral completeness, making it minimally viable.

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, and the schema has 100% coverage by definition. The description adds no parameter-specific details, but the baseline for zero-parameter tools is 4 since there is nothing to clarify.

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 'List all derivation sessions' using a specific verb and resource, and the 'all' clarifies scope. This distinguishes it from siblings like derivation_list_saved or derivation_search_saved, which focus on saved or filtered sessions.

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 about when to use this tool versus alternatives like derivation_list_saved or derivation_search_saved. The description does not mention any exclusions or conditions, leaving the agent to infer usage merely from the name.

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