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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. Beyond that the description adds real value by naming the underlying endpoint (GET /rotas/ministry_members) and clarifying that the 'person' field may be a contact or child id, which is non-obvious behavior for this data shape.

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 plus an endpoint line: purpose and payload first, then the follow-up lookup hint, then the API path. Nothing is padded and nothing important is buried.

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?

With no output schema, the description carries the burden of explaining returns, and it does list the key fields an agent needs to interpret results, while pagination is fully handled by the schema's next_page hint. A quick note on default ordering or result volume would make it fully self-sufficient, but nothing critical is missing for correct invocation.

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% (page, order_by, per_page, role_ids, team_ids, ministry_ids are all documented in-schema), so the baseline is 3. The description restates the id-based filtering fields but adds no syntax, defaulting, or combination semantics beyond what the schema already supplies.

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 and resource ('List who serves in rota ministries') and enumerates the return payload (ministry id, team id, person id, role ids), which cleanly separates it from sibling listers like list_ministries and list_ministry_teams that cover the ministry/team entities themselves rather than their membership.

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?

It gives actionable workflow context: resolve the returned person id via get_contact or get_child, and it implicitly frames the tool as the membership-lookup step. It stops short of explicit when-not guidance or naming a sibling alternative, so it is clear context without exclusions.

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