Air agent manifest

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

No annotations provided, so description bears full burden. It discloses return contents but not behavioral traits (e.g., read-only, side effects, auth). For a manifest retrieval, likely non-destructive, but not stated. Lacks details on caching, rate limits, or privacy.

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?

Single sentence listing many return components. Efficient and front-loaded, but could benefit from structuring as bullet points for clarity. No redundant words.

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?

Description lists return components but no output schema, so agent lacks format details. For a tool that likely serves as documentation, it could be more complete (e.g., typical usage scenario). No annotations to guide safety or behavior.

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?

One optional parameter 'client' with enum and description in schema. The tool description does not add extra meaning beyond schema's 'Optional client name for tailored manifest hints.' Schema coverage is 100%, so baseline 3.

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?

Description clearly states the tool returns 'wellness-air agent manifest' and enumerates specific contents (tool list, clients, env vars, etc.). It distinguishes from siblings like air_capabilities or air_privacy_audit by listing broader manifest contents.

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?

No explicit guidance on when to use this tool vs. siblings. The description implies usage when the full manifest is needed, but lacks 'use when' or 'use instead' instructions. With 17 siblings, more context would help.

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