Google Health Agent Manifest

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds unique behavioral context by stating it does not call Google Health APIs or expose secrets, which is beyond the annotation hints and clarifies its non-destructive, offline nature.

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 brief sentences convey the essential purpose and a key constraint. Every word is meaningful; no redundancy or filler.

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?

The tool has an output schema (not shown) and only 2 enum parameters. The description is adequate for a simple manifest-retrieval tool, but given the large sibling set, more detail on when to use this versus other info tools would improve completeness.

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 coverage is 0%, meaning the description adds no explanation of the two parameters (client, response_format). Although they are enums with defaults, the description does not clarify their purpose or usage, leaving the agent with no guidance beyond 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?

Explicitly states it provides 'machine-readable install, runtime and client guidance for AI agents' with the caveat of not calling Google Health or exposing secrets. This specifies a clear verb (provides guidance) and resource (manifest data), distinguishing it from data-access or mutation siblings.

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?

Description only mentions what the tool does not do ('Does not call Google Health or expose secrets'), but fails to state when to use it or how it compares to the other 24 sibling tools. No explicit when-to-use or alternative tool references.

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