getCurrentEnumerationOptionsForDocument

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

No annotations provided, so the description must fully disclose behavior. It states 'returns a list of selected options' implying a read operation, but does not mention pagination (though schema includes page_size/page_number), revision handling, or response structure. Insufficient for an unannotated tool.

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?

Single sentence, front-loaded with key action and resource. No unnecessary 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?

Missing details: no output schema, no explanation of pagination behavior, return format (e.g., list of option IDs/names), or error conditions. For a tool with 7 parameters and no annotations, the description is too minimal.

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?

All 7 parameters are described in the schema (100% coverage), so the description adds no extra meaning beyond the schema. The description does not explain how parameters like 'fieldId' relate to enumeration fields or how 'revision' affects results. Baseline 3 as schema does the work.

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 it returns 'selected options for the requested field in the specified Document', identifying the verb (Returns) and resource (list of selected options). However, it does not differentiate from the sibling tool 'getAvailableEnumOptionsForDocument' which returns all available options, but the context of 'selected' implies current values.

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 guidance on when to use this tool versus alternatives like 'getAvailableEnumOptionsForDocument' or 'getCurrentEnumOptionsForWorkItem'. The description lacks any usage context or exclusions.

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