Air profile get

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 reinforces 'Read-only' and adds valuable behavioral context: the file location, what fields it surfaces, and the consumer of this data. No contradictions with annotations.

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?

Three sentences, each earning its place: location, read-only flag, and purpose/content. No fluff, no repetition of schema data, and the most critical fact (this returns a profile) is front-loaded.

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 simple read-only tool with one optional parameter, the description fully equips an agent: it names the exact path, the fields returned, the reason an agent would call it, and the safety profile is confirmed via annotations. No output schema is needed because the description adequately describes the payload's nature.

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 input schema documents the only parameter 'privacy_mode' with a complete enum and a description, achieving 100% schema coverage. The tool description does not add further detail about this parameter, so it meets the baseline without exceeding it.

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 description states a specific verb ('Returns'), a specific resource (the shared Delx Wellness profile with exact path), and the key contents (preferred location, sensitivity flags, units). It clearly distinguishes this read tool from its sibling 'air_profile_update' by focusing on retrieval rather than modification.

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?

The description provides a clear usage context: this profile is used so wellness-air can choose tighter AQI thresholds. It does not explicitly mention alternatives or exclusions, but the read-only nature and the presence of the sibling 'air_profile_update' make the boundary obvious for an agent.

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