list_document_enum_options

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

Discloses that tool returns FULL set, type-agnostic fallback with '~', and silent fallback for unknown types. Adds value beyond readOnlyHint annotation by detailing operational quirks.

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 short paragraphs, front-loaded with purpose, every sentence adds value. No redundant words.

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?

Covers crucial context: when to use (before update), what it returns (full set), fallback behavior. With output schema present, return value coverage is adequate. Pagination is handled by schema.

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?

With 60% schema coverage, description explains field_id as enum fields (status/type/custom) and document_type fallback behavior. Adds meaning beyond schema entries. Page size/number not detailed but schema handles them.

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 uses specific verb 'List' and resource 'valid enum options for a document field', and distinguishes from sibling by stating 'Document fields only.'

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?

Explicitly advises calling before update_document and warns about Polarion behavior (unknown ids persist as ghosts). Provides guidance on verifying type id. Could explicitly contrast with list_work_item_enum_options but sibling context is clear.

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