connection_request

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

Annotations indicate destructive and non-idempotent behavior. Description adds detail on mechanism (HTTP connection request), return codes (200/504), and that it triggers a CWMP session without queuing. 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?

Description is multi-sentence but well-structured: purpose, usage, mechanism, returns, example, limitations. Each sentence adds value, though slight verbosity could be trimmed.

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?

Despite no output schema, description explains return values and behavior. Covers example, limitations, and what the tool does not do (queuing). Adequate for the tool's simplicity.

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 provides 100% coverage for device_id with format description. Description adds value by giving an explicit example and source for valid IDs, enhancing schema meaning.

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 'Send a connection request to wake a CPE device' and specifies context like executing pending tasks, applying presets, or forcing parameter refresh. Distinguishes from sibling tools like reboot_device or refresh_parameter by focusing on immediate contact trigger.

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 when-to-use scenarios (immediate contact needed). Mentions limitations (NAT, reachability) and that it does not queue a task. Could improve by explicitly stating when not to use and listing 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.