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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them by disclosing the auth model: @PermitAll resources still gated by ApiKeyScopeFilter, which categories need `metadata:read` versus `automations:read`, and that a missing scope yields 403 with a concrete remedy. That is exactly the kind of failure-mode context annotations cannot express.

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 critical guidance (call before guessing, avoid 400s) is front-loaded, and the bulleted category structure is easy to scan. It is long, and some of the emoji-selection preference detail is more verbose than an agent strictly needs, but almost every line carries operational value.

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?

With no output schema, the description correctly explains what comes back ('the authoritative set of values the backend accepts') and how each category's rows are keyed. Permissions, scope requirements, and per-category purpose are all covered, leaving no obvious gap for a read-only list tool.

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 already 100%, so baseline would be 3, but the description adds real semantic content for the `category` enum — each of the ten values is explained with the shape of its output and, critically, how its values are consumed downstream. This turns a bare enum list into actionable parameter guidance.

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 first sentence gives a specific verb and resource ('List a Dutify reference-data enum') and immediately scopes it with concrete examples of the enums covered. It is clearly distinguished from siblings such as pm_list_task_types or pm_create_custom_field, which are named as consumers rather than alternatives.

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?

It states an explicit when: 'call this BEFORE guessing enum strings on a create/update payload to avoid 400s.' Each category block adds its own usage rule (e.g. use the `identifier` as the `fieldType` for pm_create_custom_field, use typeId for /v1/views), so the agent knows both when to call and what to do with the result.

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