bernstein_tasks

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states the return type (JSON array) and the optional filter, but reveals nothing about side effects, authentication requirements, rate limits, or pagination. As a read operation, it likely has no destructive effects, but this is not specified.

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 concise with a clear Args/Returns structure. Every sentence serves a purpose, though the 'Returns:' line could be more specific about the output schema format.

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 list tool with one optional parameter and an existing output schema (context indicates it exists), the description covers the main use case adequately. However, it lacks details on filtering behavior or edge cases like multiple status values.

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 0%, so the description must add meaning to the parameter. It lists the possible filter values (open, claimed, etc.), which is helpful but not exhaustive or structured. The default null is implied but not explained in context.

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's function as listing tasks from the Bernstein server, with a specific verb ('List') and resource ('tasks'). It distinguishes itself from sibling tools like bernstein_approve or bernstein_create_subtask, which have different actions.

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 on when to use this tool versus alternatives. The description does not mention scenarios where a different tool might be preferred, nor does it explain when to omit the status filter.

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