Update a trunk

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

Adds significant behavioral context beyond annotations: the trunk is excluded from capacity-sum check, POI assignment is silently ignored, and Step-up MFA is required. No contradiction with annotations (idempotentHint=true is consistent with update semantics).

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 succinct, front-loads the main purpose, and adds relevant details without extraneous text. Slightly verbose with error list but still 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?

Covers errors, prerequisites, and behavioral quirks. Lacks description of return value or side effects, but given no output schema, this is acceptable. Could be more complete for a complex tool.

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 descriptions cover all 10 parameters comprehensively (100% coverage). The tool description adds minimal additional meaning beyond echoing schema fields, so baseline score 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 states 'Update an owned trunk's settings' with specific fields listed (name, auth type, capacities, SIP config). It distinguishes from sibling operations like trunk_create and trunk_delete.

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?

Provides explicit prerequisite ('Use trunk_list first to find the trunk id') and mentions special conditions (POI silently ignored, Step-up MFA required). Does not explicitly state when not to use or list alternatives, but context is clear.

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