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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the returned field names (name, company, email, phone, type, label) which is useful, but says nothing about pagination behavior, result limits, or that filters silently ignore bad input (that is only in the schema).

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 compact clauses with no wasted words; the purpose and returned fields are front-loaded. It is perhaps over-terse, but nothing is filler.

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?

The rich parameter schema and annotations carry most of the load, and the description adds the return field list. However, with no output schema, it omits pagination/next_page behavior and filtering guidance that an agent calling this list tool would benefit from.

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%, so the baseline is 3. The description lists entity fields but does not explain the parameters themselves beyond what the schema already documents in detail (filters, sort_by, page, limit).

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?

States a specific verb (List) and resource (contacts) and clarifies the resource's scope with examples (customers, suppliers, vendors). The field list and GET /contacts endpoint pin down what it returns, making it easy to distinguish from write siblings, though it never names farmbrite_get_contact as the single-record alternative.

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?

There is no guidance on when to use this versus farmbrite_get_contact or farmbrite_create_contact, and no notes on pagination workflow or when to prefer the filters parameter. Usage is only inferable from the verb 'List' and the endpoint hint.

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