get_archive_health

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds that an admin search-engine overview may be included, but it does not explain what triggers 'full mode' or any permission implications of the admin view.

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, front-loaded sentence that states the primary resource first. It is concise, but 'full mode' is referenced without explanation, which is a minor clarity cost rather than a verbosity problem.

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 health response shape is left undescribed. The 'full mode / admin search-engine overview' behavior is mentioned but not tied to any parameter or condition, so an agent cannot reliably know how to request it or what it will return.

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 schema already documents sourceId at 100% coverage as an optional ingestion source ID. The description adds some meaning by connecting the optional parameter to source health, but the connection is implicit and 'full mode' has no corresponding parameter in 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?

Names a specific action ('Get') and a clear resource: global index health, optional source health, and an admin search-engine overview. It reads as distinct from the sibling get_archive_stats, though 'full mode' is left undefined which prevents a 5.

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?

Provides no guidance on when to choose this tool over siblings such as get_archive_stats, search_emails, or list_ingestion_sources. The only usage hint is that source health is optional, which is closer to parameter guidance than tool-selection guidance.

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