sys_tr069

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

With no annotations, the description carries full behavioral burden. It does disclose that this is a mutation ('write') and that confirmation is required, which is meaningful context beyond the tool name. However, it omits where confirmation tokens come from, whether changes are reversible, and what side effects may occur.

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 a single compact sentence that front-loads the core action and the key warning about confirmation. There is no filler or repetition. While more detail could be added, the existing wording is appropriately concise.

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 write tool with a confirmation requirement, the description is incomplete: there is no output schema, no annotations, and no explanation of how to obtain or supply confirm_token/confirmation_id, or what user_code is for. An agent cannot confidently execute the confirmation workflow based on this definition alone.

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 0%, so the description must compensate for the four parameters, but it only implicitly maps 'Enable/disable' to the 'onoff' parameter. The roles of user_code, confirm_token, and confirmation_id are not explained in either the schema or the description, leaving the agent to guess from parameter names alone.

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 states a clear action ('Enable/disable') and a specific resource ('TR-069'), so an agent can tell what the tool does. It also notes this is a write operation, which adds a useful scope signal. However, it does not differentiate this tool from the similarly named sibling swm_tr069, which may also operate on TR-069.

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 'write — requires confirmation' parenthetical implies this is for changing state, not for reading status, and signals that confirmation is a prerequisite. But the description does not explicitly say when to prefer this tool over alternatives or when not to use it. The usage guidance is implied rather than stated.

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