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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds only the raw endpoint path 'GET /fields' and says nothing about what a lead-vs-client field set contains or whether results are paginated.

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?

Very short — two fragments — so nothing is bloated, but it is under-specified rather than concise. The 'GET /fields' endpoint string consumes half the text without informing tool selection.

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?

There is no output schema, so the description should convey what a returned field definition looks like (ids, names, types) and how the two field sets differ. Neither is present, leaving the agent unable to anticipate the response for a tool it must otherwise guess about.

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 100% and the single 'type' parameter is already documented with its enum, so the baseline is 3. The phrase 'for leads or client folders' loosely echoes the enum values but adds no format or default behavior detail 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?

Names the resource (custom fields) and its scope (leads or client folders), so an agent can infer this is a read of field definitions. However, the sentence is a noun phrase with no verb, and nothing distinguishes it from sibling list tools such as nocrm_list_predefined_tags or nocrm_list_pipelines beyond the resource name.

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 indication of when to call this versus the many other list_* siblings, no prerequisites, and no note on whether the type filter is required or what omitting it returns. The agent must infer all call conditions.

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