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

readOnlyHint=true already tells the agent this is a safe read with no side effects, lowering the bar. The description adds the date-range sync use case but says nothing about result volume, pagination semantics, or how the custom_field_id/custom_field_value pair must be used together.

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?

Compact and front-loaded: purpose, filter list, usage hint, endpoint mapping, with no filler. The em-dash filter enumeration is slightly dense but every clause carries information.

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 10-parameter list tool with no output schema, the description covers what can be filtered and one use case but omits result-set behavior and paging expectations an agent would need when syncing, and never positions itself against the search sibling.

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 80%, so the schema already documents most parameters including defaults and ranges. The description restates the filter categories the schema already names and adds no syntax, pairing rules, or default behavior of its own, making baseline 3 correct.

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 (constituents) and enumerates the filter dimensions (Id, type, favorites, last-modified, custom field) plus sorting. It does not, however, distinguish itself from the sibling bloomerang_search_constituents, which an agent could easily confuse with this tool.

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?

'Good for syncing recent changes' gives one concrete usage scenario, implying the last_modified filter path. But there is no explicit when-not guidance and no mention of search_constituents or get_constituent as alternatives, so selection between the three constituent-reading siblings is left to inference.

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