Air profile get

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

With no annotations provided, the description carries the full burden. It explicitly states the tool is read-only, returns specific data (location, sensitivity flags, units), and references the file path. This is transparent for a simple read operation, though it could mention lack of side effects.

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?

The description consists of two concise sentences. The first states the core action and read-only nature, and the second provides the purpose and content. Every word adds value with no redundancy.

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?

Given the tool has no output schema and no parameters, the description adequately explains the return value contents and purpose. However, it does not specify the response format (e.g., JSON structure), which could be slightly more complete.

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 has zero parameters, and schema coverage is 100%. The baseline for 0 params is 4. The description adds meaning beyond the schema by explaining what data the tool returns and why it is useful, earning a 5.

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 clearly states it returns the shared Delx Wellness profile file, lists its contents (location, sensitivity flags, units), and explains its purpose for AQI thresholds. It distinguishes itself from the sibling tool `air_profile_update` by explicitly noting it is read-only.

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 clearly indicates the tool is for reading the profile and implies it should be used when you need profile data. It does not explicitly state when not to use it or provide alternatives, but the read-only label and sibling tool name `air_profile_update` provide sufficient context.

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