crm_get_picklist_fields

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

No annotations are provided, so the description carries the full burden. It implies a read-only 'get' operation and narrows the scope to picklist fields, but does not disclose return format, pagination, or any side effects. The behavioral traits are clear enough for a simple getter, but not richly described.

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 description is a single, front-loaded sentence with no wasted words. It immediately states the action and scope, then adds a helpful use-case hint. Perfectly concise.

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 one-parameter getter with no output schema, the description is mostly complete. It explains what the tool does and its intended use case. It could ideally clarify the exact return structure (e.g., list of field definitions), but the tool name and description are sufficient for basic understanding.

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?

The single parameter module_name has 100% schema description coverage ('Name of the module'), so the schema already provides the meaning. The description reinforces that it is a 'specific module' but adds no extra syntax or format details beyond the schema.

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 a specific action ('Get only picklist fields') and resource ('for a specific module'), and adds a specialized use case ('optimized for finding disposition/status fields'). This distinguishes it from sibling tools like crm_get_module_fields (all fields) and crm_get_picklist_values (values of picklist fields).

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 gives clear context on when to use this tool: when you need only picklist fields, and specifically for locating disposition/status fields. It does not explicitly name alternative tools or state when not to use it, so it falls just short of a 5.

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