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 and repeatability profile is fully covered. The description contributes the API endpoint (GET /account/sites) and the downstream-filtering semantics, but says nothing about pagination, auth requirements, or result limits.

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?

Three short sentences, front-loaded with purpose, followed by the useful downstream context and the API path. No filler, and the most decision-relevant information (what it lists, what the ids are good for) comes first.

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 zero-required-parameter list tool with no output schema, the description compensates by enumerating the returned fields and explaining the practical use of the result. Combined with rich annotations, an agent has everything needed to call and use this correctly.

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% for the single 'ids' parameter, which already documents the numeric ChurchSuite ids and the 100-item cap. The description adds only indirect meaning by noting that site ids are reused as filters elsewhere; it gives no format or edge-case guidance for this parameter beyond the schema. 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 (List) and resource (church's sites), then disambiguates the resource with a parenthetical glossary ('campuses/congregations') and enumerates the returned fields (id, name, initials, address). An agent can tell exactly what this returns and can distinguish it from the many other churchsuite_list_* siblings.

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?

Explains why the tool matters: 'Site ids filter contacts, children, groups, events and plans,' which tells the agent to call this first when it needs site ids for downstream filtering. It does not name a specific alternative or state when-not to use it, so it falls short of a 5.

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