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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds that this is a GET endpoint and hints at the incremental-sync pattern, but says nothing about pagination behavior, the 50-record cap, or result shape beyond what the schema already states.

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 sentences with the filter enumeration front-loaded and the sync use case last. The endpoint reference is arguably redundant given the tool name, but the description carries no 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?

For a 10-parameter, zero-required list tool with no output schema, the description covers the filter space and a motivating scenario, and pagination/limit details live in the schema. It is adequate to call the tool correctly, though a note on how results are paginated or capped would have closed the remaining gap.

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 most parameters are already documented (ids, skip, take, is_favorite, last_modified, custom_field_id/value). The description's filter list (Id, type, favorites, last-modified, custom field) largely restates those and lumps sorting into one phrase, adding little 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?

States a specific verb+resource ('List constituents') and enumerates the filter dimensions it supports, plus names the underlying endpoint (GET /constituents). It does not explicitly distinguish itself from the sibling bloomerang_search_constituents, so an agent still has to infer which listing-style tool to pick.

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?

Offers one concrete usage hint ('Good for syncing recent changes') that implies the last_modified filter, but gives no when-not guidance and never mentions bloomerang_search_constituents or bloomerang_get_constituent as alternatives. Usage is implied rather than specified.

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