update_application_pool

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description goes beyond that by disclosing a non-obvious silent data-loss behavior: file_types is dropped from the payload whenever enable_auto_update_file_types is enabled, because Horizon rejects that combination on update. This is exactly the kind of hidden side effect that annotations cannot convey.

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 opening sentence is front-loaded and complete. The second paragraph is denser and slightly meandering in its preamble about what Horizon returns before reaching the actionable rule, but every sentence carries information the caller needs.

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?

An output schema exists, so return values need not be explained. However, for a destructive update tool the description does not state whether 'spec' is a full replacement or a partial patch (the schema only implies read-modify-write), nor does it mention permission requirements. The critical file_types gotcha is well covered, but these gaps remain.

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%, so the baseline is 3, but the description adds real meaning about the nested 'spec' object — specifically that its file_types member may be silently stripped. That informs how an agent should build the spec payload in a way the schema does not.

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?

States a specific verb and resource: 'Update an existing application pool's configuration.' This clearly distinguishes it from create_application_pool, delete_application_pool, and get_application_pool by name alone. It stops short of explicitly contrasting itself with those siblings in prose, but the operation is unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance, nor a named alternative. The only implied guidance is that this applies to an 'existing' pool (as opposed to create), and the schema mentions retrieving current config first with get_application_pool. A conditional caveat about auto-update is given, but not framed as selection guidance.

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