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

The readOnlyHint annotation already establishes this is a safe read operation, and the description adds that it is full-text and which entities/fields are covered plus the underlying endpoint. It does not disclose result caps (take max 50), ordering, or result shape, so it adds moderate context beyond annotations but not rich behavioral detail.

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 tight sentences front-load the core capability followed by the workflow hint and endpoint reference. Every clause carries signal, though the trailing 'Bloomerang: GET /constituents/search' is marginally redundant for an agent.

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 read-only search with a fully documented schema and no output schema, the description covers purpose, scope, and the downstream workflow sufficiently. Minor gaps around pagination behavior and result ordering remain but are largely carried by the schema.

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 all four parameters (search, type enum, skip, take) are already documented in the schema. The description adds no syntax, matching behavior, or example values beyond what the schema provides; baseline 3 applies.

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 ('full-text search across constituents') and enumerates the entity types (individuals, organizations, households) and searchable fields (name, email). It implies a distinction from list_constituents by emphasizing full-text search, but never names that sibling explicitly, so the differentiation is left to inference.

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?

'Start here to find a donor's Id' gives a useful workflow cue (a search-then-get flow), implying this precedes bloomerang_get_constituent. However it offers no explicit when-not-to-use guidance or contrast with bloomerang_list_constituents for browsing, so usage is only implied.

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