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

The readOnlyHint annotation already covers the safety profile, so the bar is lower, and the description adds real value beyond it: it enumerates the returned fields (id, label, status, source_attributes, destination_attributes), which matters because no output schema exists, and it maps the tool to the underlying 'GET /syncs' call. It omits pagination behavior and any auth/rate-limit context, so not a 5.

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 with zero filler: purpose and resource definition first, then return shape, then the underlying endpoint. Every clause carries information and the most decision-relevant content is front-loaded.

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, two-parameter list tool with annotations covering safety, the description supplies the resource definition, the return fields (compensating for the missing output schema), and the API mapping. Only pagination semantics and guidance for choosing this over census_get_sync/census_list_sync_runs are absent, which are minor given 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% – both page and per_page are documented in the schema as pagination controls. The description adds nothing about pagination defaults, limits, or ordering, so the schema does all the work and the baseline of 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 syncs') and goes further by defining what a sync is ('maps a source model to a destination object and keeps them in sync'), which meaningfully separates it from the singular census_get_sync and from census_list_sync_runs. It stops short of explicitly naming siblings, so it is clear but not fully differentiated.

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?

Usage is only implied: the plural 'List' plus the enumerated return fields signal this is the enumeration/overview tool, and it contrasts implicitly with census_get_sync for a single record. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the routing itself.

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