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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds little beyond that, only the backing endpoint 'GET /site/list' and the fact that results can be filtered; it says nothing about pagination or result shape that the annotations don't already imply.

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?

A single compact sentence that front-loads the action and resource, then lists filter axes, then names the endpoint. No filler and nothing redundant.

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 9-parameter read-only list tool with strong schema coverage, the description plus annotations give an agent enough to invoke correctly. It stops short of describing the return payload or pagination flow at any point, which matters slightly given there is no output schema, but the 'page' parameter's next_page hint partially compensates.

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 89%, so the schema already documents the 9 parameters in detail (defaults, ranges, wildcard search, next_page chaining). The description merely names filter categories that map onto those same parameters, adding no syntax or format detail 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 pair (list/search) and resource (sites), plus a helpful gloss that a site is a customer's location. It does not, however, distinguish itself from close siblings like synchroteam_get_site or synchroteam_list_customers, so the agent must infer the boundary.

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?

The mention of search dimensions (name, customer, active flag, change time) implies when this tool is useful, but there is no explicit when-to-use versus get_site (single-record retrieval) or any stated exclusions. Guidance is inferable rather than stated.

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