Air profile update

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

Given no annotations, the description discloses key behavioral traits: partial patch (not full replacement), requirement for explicit user intent, rejection of sensitive fields. This goes beyond the raw schema and provides safety and usage context, though it does not detail error handling or 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?

Two sentences, front-loaded with core purpose. Each sentence adds essential information with no redundancy. Highly efficient.

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 tool with 2 parameters and no output schema, the description covers purpose, required parameter, and input constraints. It could mention return value (e.g., success status) but is otherwise complete given the complexity level.

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 100% with descriptions for both parameters. The description adds valuable constraints beyond schema: the patch parameter rejects fields containing sensitive keywords like oauth/token/secret, which is not in the schema. This enhances understanding of valid input.

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 'Persist a partial patch to the shared Delx Wellness profile', specifying the verb (persist/update) and resource (shared Delx Wellness profile). It distinguishes from sibling air_profile_get (read) by indicating this is a write operation.

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 explicit context: requires explicit_user_intent=true and rejects sensitive fields. It implies the tool should only be used when the user explicitly requests to save/update profile data, but does not explicitly state when not to use or mention alternatives like air_profile_get for reading.

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