zentao_list_bugs

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

No annotations are present, so the description carries the full burden. It discloses the read-only nature upfront and the behavioral quirk that scope depends on user phrasing ('all' vs default). This goes beyond basic purpose and is helpful. It lacks details on error conditions or return format, but the core safety trait is disclosed.

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 sentences, front-loaded with the read-only verb, followed by scope logic and filter summary. No fluff; every sentence adds operational 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?

Given no output schema and no annotations, the description provides essential context: default scope, condition for all scope, and supported filters. However, it omits return-behavior details (pagination total, ordering, possible errors), leaving some aspects to inference. It is adequate for a list operation but not exhaustive.

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 a filtered overview (pagination, product, project, execution, status, keyword) that maps to the schema but does not add semantics beyond a summary. Baseline 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 states a specific verb-resource pair ('read-only query ZenTao Bug list') and adds behavioral specifics about default scope. It is distinguishable from zentao_get_bug and zentao_resolve_bug, though not explicitly contrasted with zentao_search_bugs, which limits differentiation from that sibling.

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 explains the default scope (assigned to current MCP account) and the trigger for broader scope ('all bugs'), which is useful. However, it does not explicitly route the agent to sibling tools such as zentao_get_bug for single-bug lookups or zentao_search_bugs for search-like queries, so exclusions are absent.

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