list_synced_metrics

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

With no annotations, the description carries the full burden and does substitute for readOnlyHint by stating "Read-only catalog observation." It also discloses what the response contains (metric types, provenance, missing-data caveats) and a scope limit (no clinical interpretation), which is strong for a zero-argument tool; it stops short of mentioning permissions, rate limits, or pagination.

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 sentence that front-loads the operation type and packs purpose, return contents, and scope caveat without a wasted word. Nothing could be trimmed without losing meaning.

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 no-parameter, no-output-schema read-only listing, the description covers operation, safety profile, returned fields, and an interpretation caveat. It is nearly complete; only disambiguation from the near-identical sibling and any call prerequisites are missing.

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?

The tool takes zero parameters, so there is nothing to document and the baseline is 4. The input schema confirms an empty object with additionalProperties false.

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?

"Listing synced metric types, provenance, and missing-data caveats" gives a specific verb plus a concrete resource and even names the payload. It is clear on its own, but it does not distinguish itself from the very similar sibling list_supported_timeseries_types, so an agent must guess which catalog to use.

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?

"Read-only catalog observation" and "no clinical interpretation" imply when the tool is appropriate (metadata inspection, not clinical analysis), which is genuine guidance. However there is no explicit when-to-use statement, no prerequisites, and no routing to alternatives such as list_supported_timeseries_types or get_timeseries.

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