list_tasks

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

Since no annotations are provided, the description must disclose behavioral traits. It only mentions scoping to the user's API key but omits details like pagination behavior (though page/limit params exist), rate limits, side effects, or error handling. This is insufficient for a tool with no annotation context.

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, efficient sentence with no redundancy. However, its brevity sacrifices necessary detail; a slightly longer description could provide parameter hints or usage context without being wasteful.

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?

Despite having an output schema (not provided), the description fails to explain the return structure or pagination logic. For a listing tool with four optional parameters, the description should cover common use cases, such as how search and source affect results, which it does not.

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 0% description coverage, and the tool description does not explain any of the four parameters (page, limit, search, source) beyond what the schema defines. The description adds no semantic value about their purpose, valid values, or default behavior.

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?

Description clearly states the verb 'List', the resource 'OcrPlane tasks', and the scope 'for the configured API key user'. It effectively distinguishes from sibling tools like get_task_status or parse_document by indicating it returns a list rather than a single resource.

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 on when to use this tool versus alternatives such as get_task_status or parse_document. The description does not mention prerequisites, such as needing to have previously uploaded a document, nor does it explain what scenarios favor listing tasks over retrieving specific ones.

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