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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds genuinely new behavioral facts beyond them: "Reading it calls no provider and changes nothing" and "LiveCRM runs it daily; nothing here starts it." This clarifies cost/side-effect profile that annotations alone don't cover.

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?

It is front-loaded with the headline value, but the bulk is one very long, comma-spliced sentence enumerating return fields and stalling causes. Since no output schema exists, some of that content earns its place, but the structure is dense and hard to scan.

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 correctly carries the burden of describing return values (headline, four measures, counts, trend, stalling causes) and the behavioral context. It is nearly complete, though it omits any contrast with get_operational_health, a similarly-scoped sibling.

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?

There is one parameter (connection_id) with 100% schema description coverage; the schema already documents it and even tells the agent to call list_crm_connections first. The description adds no syntax or format detail beyond the schema, 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?

The opening clause states a specific verb and resource: it returns "The connection's Health Score as LiveCRM measured it at its last daily run." It also explicitly distinguishes itself from the readiness siblings by directing setup needs to get_readiness_recommendations. An agent can tell what it retrieves without opening the 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?

It gives clear context (daily-run snapshot, "nothing here starts it") and routes one adjacent need to an alternative ("What to set up is the readiness scan's: call get_readiness_recommendations"). However, it never distinguishes itself from the closely-named sibling get_operational_health or get_readiness_scan, so an agent still has to guess among those.

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