ass_list_attachments

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

With no annotations, the description carries the full burden, and it does disclose substantive behavior: magic-byte sniffing to classify payloads, base64 validity checking, and the encoded*3/4 size fallback when decoding fails. It does not explicitly state that the operation is read-only or side-effect free, but 'List' plus the computed metadata makes the nature clear enough.

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 one-line summary is well front-loaded and the Args/Returns split is clean. However, the Returns block enumerates roughly a dozen fields in dense prose, and since an output schema already exists this detail largely duplicates structured data rather than earning its place.

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 two-parameter, zero-required read tool with an output schema, the description covers purpose, both parameters with defaults, and the key computed behaviors. The only real gap is routing guidance versus sibling listing/font tools, which is scored separately.

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 0%, so the description must compensate, and it does: doc_id is documented as an id or None for the current document, and kind documents the accepted spellings ('font'/'fonts', 'image'/'graphics') and that None returns both sections. These accepted-value aliases are not in the schema and are genuinely useful.

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?

Specific verb (list) plus resource (attachments), with the exact source sections named ([Fonts]/[Graphics]) and the non-obvious behavior (magic-byte sniff) front-loaded. An agent can immediately distinguish this read tool from ass_add_attachment, ass_extract_attachment, and ass_remove_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 kind parameter description implies how to restrict the listing, which gives in-tool usage context. However, there is no guidance on when to prefer this over related siblings such as ass_list_fonts, ass_fonts_used, or ass_check_font_substitution, leaving alternative selection to inference.

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