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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the response carries the credential and is only accessible by the device owner, is one channel per request, is never cached, and documents the two error cases and their meaning.

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 dense but every sentence earns its place: definition, return format, security and caching behavior, then error handling. The key facts are front-loaded in the opening sentence, and the prose does not waste words on restating the tool name.

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?

Given the tool has no output schema and no annotations, the description is unusually complete: it explains what is returned, the credential sensitivity, caching behavior, error codes, and recovery action. Nothing essential for correct invocation is missing.

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%, so the baseline is 3. The description does not add much parameter-specific detail beyond the schema, aside from framing id and collector as a single collector channel; that is a minor extension, not a necessary compensation.

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 the tool returns the saved setup for one collector channel, specifically the last generated setup whose credential is accepted. It also distinguishes itself from list routes by stating they never include the credential, so an agent can tell it apart from list_device_inputs and similar siblings.

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 explicitly states when to use it: to copy or reinstall files without rotating the credential. It also warns that list routes never include it and gives a concrete fallback action—generate a new setup via POST /api/ambientes/:id/inputs—when 404 or 409 errors occur.

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