批量获取 TAPD 需求详情

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

Annotations declare readOnlyHint=true, consistent with 'get' behavior. Description adds useful context: returns detailed content including comments, attachments, images, videos, and status with workflow Chinese name. No contradictions, but could mention rate limits or auth requirements.

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 concise sentences: first states core purpose and included content, second adds detail on status format. No redundant information. Front-loaded with key action and resource.

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 read-only retrieval tool with no output schema, description covers returned fields (description, comments, attachments, images, videos, status with workflow name). Missing details on pagination, error handling, or response structure, but adequate for typical use.

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% with both parameters described. The description does not add significant new semantics beyond the schema; it merely restates the batch retrieval nature. Baseline 3 is appropriate as description doesn't enhance parameter understanding.

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 it retrieves full content of multiple TAPD stories including descriptions, comments, attachments, images, and videos. Title '批量获取 TAPD 需求详情' reinforces purpose. This distinguishes from siblings like tapd_list_stories which likely provide summaries.

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 explicit guidance on when to use this tool vs alternatives. Does not mention when not to use (e.g., for single story retrieval, or for updating stories). No comparison to siblings like tapd_get_bugs or tapd_list_stories provided.

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