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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by naming the underlying endpoint (GET /rotas/ministries) and enumerating the fields returned, which matters because no output schema exists; it does not contradict any annotation.

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?

One sentence plus a short API note, with the verb and resource front-loaded and the field list compressed into a single parenthetical. Nothing is padded or repeated.

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 usefully compensates by enumerating returned fields, and the schema fully covers inputs and pagination. The only real gap is that filtering capability goes unmentioned in prose, but an agent can still call it correctly from the schema alone.

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 six parameters (q, ids, page, per_page, site_ids, statuses) are fully documented in the schema, including pagination semantics and next_page usage. The description adds nothing parameter-specific, so the 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 and resource — 'List the Rotas module's ministries' — and even parenthetically instantiates it (worship team, welcome team), so an agent knows exactly what objects come back. It stops short of differentiating from close siblings such as churchsuite_list_ministry_members and churchsuite_list_ministry_teams, which is what a 5 would require.

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 when-to-use statement, no note that the tool supports fuzzy search / id / site / status filtering, and no routing to alternative tools. The description reads as a pure definition rather than guidance, leaving the agent to discover filtering behavior only by opening the schema.

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