List Zentra tasks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only adds one behavioral note about omitting 'tag', but does not disclose the return format, pagination, read-only nature, potential errors, or any side effects. This is a significant transparency gap for a tool with no annotation support.

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 two sentences long, front-loaded with the primary action, and contains no redundant or filler wording. Every sentence contributes useful information.

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?

With four optional parameters and no output schema or annotations, the description is incomplete. It only mentions two of the four filter parameters (tag and status) and does not describe the output format or behavior beyond the filter logic. This leaves significant context gaps for an agent selecting and invoking the tool.

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 only 25%, so the description must compensate. It clarifies that 'tag' refers to a project tag and that omitting it returns all projects, and it mentions 'status' as a filter. However, it does not explain 'type' or 'parentId', leaving those parameters without additional semantic context beyond their raw schema definitions.

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 'Lists tasks from Zentra's production task board' with a specific verb and resource, and mentions optional filters by tag and status. This distinguishes it from sibling tools 'zentra_task_create' and 'zentra_task_move', which are write operations.

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?

Provides clear context: lists tasks from the production board, and explicitly advises omitting 'tag' to see tasks across all projects. It does not explicitly state when not to use it, but the read-only nature of listing is clear from the sibling tool names, making the context sufficient.

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