bugherd_list_tasks

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

No annotations are provided, so the description must fully convey behavioral traits. It only states that the tool lists tasks and can filter, but omits any side effects, authentication needs, rate limits, or error behaviors. For a read-only tool, this is minimally adequate but lacks depth.

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 sentence that efficiently conveys the core purpose and filtering options. It is front-loaded and contains no unnecessary words or repetition. Every clause adds value.

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?

The description, combined with the 100% parameter schema coverage, covers the tool's inputs well. However, there is no output schema, and the description does not explain the return format or fields. Given the complexity of listing tasks with filters, the lack of output details leaves a gap for the 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 coverage is 100%, so each parameter already has a description. The description adds no new semantics beyond what is in the schema; it merely restates that status uses column names from another tool. With high schema coverage, the baseline is 3, and the description does not exceed it.

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 purpose: 'List tasks (bugs/feedback) for a specific BugHerd project.' It uses a specific verb ('list') and resource ('tasks') and distinguishes from sibling list tools by implying it lists all tasks for a project, not archived, feedback-only, or taskboard tasks.

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?

The description mentions filtering capabilities and references bugherd_list_columns for status, but does not provide explicit guidance on when to use this tool versus other list tools like bugherd_list_archived_tasks or bugherd_list_feedback_tasks. The usage context is implied but not fully delineated.

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