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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the useful domain semantics of what a destination is, but discloses nothing about pagination behavior, total counts, or result shape beyond the raw endpoint reference.

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 with the core definition front-loaded and the API reference trailing. The 'Census: GET /destinations' fragment is mildly redundant but adds provenance, not enough to drop below 4.

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, fully-schematized list endpoint with no output schema, the description covers the essential purpose and domain framing. Missing return/pagination context is a minor gap given the annotations already signal a safe read.

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% and both page/per_page parameters are documented in the schema, so the description correctly defers to it. The description adds no syntax, defaults, or filtering semantics beyond what the schema already provides, so 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 (configured destination connections), then defines the resource in domain terms ('SaaS apps data is synced INTO') with concrete examples. This lets an agent distinguish it from the sibling census_list_sources without opening either schema.

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 implied by the definition of 'destination' versus 'source', which is the key distinction among the list_* siblings. However, it never explicitly says when to use this versus census_list_sources or census_get_destination, so the agent must infer the routing.

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