List Translation Tasks

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

With no annotations provided, the description carries the burden. It transparently indicates a read-only list operation with pagination, but adds no details on ordering, status scope, or return format. The term 'historical' is ambiguous and could mislead about whether in-progress tasks are included.

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?

Two short sentences with no fluff. The first sentence states the action and key feature (pagination); the second adds the 'historical' scope. Efficient and front-loaded.

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?

For a simple 2-parameter list tool with no output schema or annotations, the description gives enough to understand the operation. However, it does not explain what data is returned, what 'historical' means, or how it relates to sibling search_documents, leaving some gaps.

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 already provides 100% coverage with clear descriptions for 'limit' and 'offset'. The description's mention of pagination adds marginal value beyond the schema, so the baseline score of 3 is appropriate.

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 the tool lists translation tasks and supports pagination. 'List' sharply contrasts with sibling 'get_translation' and 'create_translation', making it easy for an agent to select it for multi-result retrieval.

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?

It conveys the core use case: listing all historical tasks with pagination. While it does not explicitly name alternatives or exclusions, the context 'view all historical translation tasks' gives clear guidance for when to use this tool.

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