list_generations

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

With no annotations, the description carries full behavioral burden. It only notes 'GET /uapi/v1/histories', which implies a read operation, but does not disclose pagination behavior, ordering, authentication requirements, rate limits, or what 'recent' means. This is insufficient for a list operation.

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 very concise and front-loads the core purpose. The second sentence, the endpoint path, is arguably an implementation detail with limited value for an agent invoking the tool, but it does not create bloat.

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 three parameters, no annotations, no output schema, and low schema description coverage, the description is incomplete. It omits parameter semantics, usage context, pagination details, and return information, leaving significant gaps for an agent.

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 33%, with only 'filter_by' having a brief description. The description does not compensate for undocumented parameters like 'page' and 'items_per_page', nor does it clarify the meaning or accepted values of 'filter_by' beyond what the schema already states.

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 states a clear verb ('List') and resource ('recent generations'), making the tool's purpose immediately understandable. It does not explicitly differentiate from siblings like get_generation or the generate_* tools, but the verb and scope distinguish it adequately.

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 such as get_generation (for a specific generation) or the generate_* tools. The description offers only the basic purpose, leaving the agent to infer usage scenarios.

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