list_workitem_attachments

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

With no annotations provided, the description carries the full burden, and it does disclose useful return context (that only metadata like size, suffix, download URL is returned, not file content) which helps an agent set expectations. However, it omits potential behavioral traits such as pagination, ordering, empty-result behavior, or permission requirements—gaps not covered elsewhere.

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 tight, front-loaded sentences: the first states the core action and the second discloses the return shape. Every word earns its place, and the useful return-field list is appropriately placed since there is no output schema. The [Project Management] prefix is minor and uncompressed.

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 2-parameter, no-output-schema list tool, the description is largely adequate—it covers what it does and what it returns (including the download URL, which directly answers likely agent questions). It falls just short of complete because it never mentions pagination, ordering, or list-size limits, which are the most likely blind spots for a list endpoint.

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 100%, so the baseline of 3 applies. The description's 'for a specific work item' reinforces the workItemId scoping but adds no new syntax, format, or semantic detail beyond what the schema already documents (工作项唯一标识, Organization ID).

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 verb (List) and resource (attachments for a specific work item) and adds return-value detail (file name, size, suffix, download URL, creator/modifier details). It's specific and unambiguous, though it doesn't explicitly contrast with sibling tools like create_workitem_attachment.

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 offers no guidance on when to use this tool versus alternatives—no mention of the obvious sibling create_workitem_attachment for uploading, no prerequisites (e.g., work item must exist, requires read access), and no exclusions. The only scoping hint is 'specific work item' embedded in the purpose, which isn't enough to constitute guidance.

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