Resetear contraseña SIP de una extensión

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

Annotations declare destructiveHint=true. The description adds a specific behavioral consequence: the phone/softphone will stop registering until reconfigured. This provides useful context beyond the annotation.

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 extremely concise, with only two sentences. The first sentence states the main action, and the second (with a warning emoji) highlights critical fallout. No superfluous information.

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 tool with one parameter and no output schema, the description explains the purpose and a key side-effect. However, it does not mention what the tool returns (e.g., the new password) or how to retrieve it, leaving the agent without complete operational context.

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?

The parameter 'extensionId' is not described in the text, and schema description coverage is 0%. The tool name implies it is the extension's ID, but the description adds no explicit meaning or usage guidance for the parameter.

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 it generates a new SIP password for the extension, using a specific verb and resource. It distinguishes the tool from siblings like pbx_update_extension by focusing on password reset.

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 implies usage when a SIP password needs to be reset, but provides no explicit guidance on when to use this tool versus alternatives (e.g., pbx_update_extension) or any prerequisites.

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