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

Annotations already provide readOnlyHint=true, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds some context about what data is included (configs, modes, guardrails, cycles) but does not disclose behavioral traits like return format, pagination, or freshness. With annotations covering the main behavioral concerns, a neutral 3 is appropriate.

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 is compact, with the core resource and contents front-loaded in the first sentence, followed by a terse disambiguation sentence. Every word contributes to orientation or disambiguation, and there is no redundancy or padding.

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 status tool with one optional parameter and no output schema, the description covers the essential scope and adds a critical disambiguation. It does not describe the response shape, but the listed contents (configs, modes, guardrails, cycles) give a reasonable expectation of what will be returned. Overall, it is complete enough for correct invocation.

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 description coverage is 100% for the single optional profile_id parameter, which already explains its meaning and optionality. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 identifies the resource as the Adaptive Optimization Engine and lists its contents: per-campaign configs, modes, guardrails, and recent optimization cycles. It explicitly distinguishes itself from automation_activity, so an agent can tell them apart. However, it lacks a specific action verb like 'retrieve' or 'list', relying on the tool name 'status' to convey the 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 gives a clear when-not signal by stating 'NOT the automation approval inbox (automation_activity)', which prevents confusion with a key sibling. It does not explicitly state when to use this tool versus other automation siblings like automation_rules or automation_recent_tasks, but the phrase 'Adaptive Optimization Engine' implies the intended use case.

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