profile_get_set

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

Annotations already provide idempotentHint and destructiveHint. Description adds that knobs are 'sealed' and lists them, but does not disclose write behavior or persistence details. No contradiction 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?

Single sentence of 21 words, no redundancy. Front-loaded with main purpose. Every word contributes meaning.

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 simple tool (3 params, output schema present, annotations), the description covers purpose, parameter context, and special knobs. Lacks only deeper behavioral details, but overall sufficient for an AI agent.

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%, but description adds value by naming the specific knobs (e.g., '10 AUTIST + wake_depth') and clarifying the effect of omitting knob on 'get'. This enriches parameter understanding beyond 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?

Description clearly states 'Read or write a profile knob' with specific resource ('11 sealed: 10 AUTIST + wake_depth'). The verb-resource combination is precise and distinguishes from sibling tools like memory_* or events_query.

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 when-to-use or alternative recommendations. The operation parameter indicates get/set, but no context on when to use this tool versus others. Siblings are sufficiently different that confusion is unlikely, but guidance is still minimal.

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