update_installation

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

Annotations are empty, so the description must bear the full burden. It only states what fields can be updated, with no disclosure of side effects, authorization requirements, idempotency, or whether changes are reversible. For a mutation tool, this is insufficient behavioral transparency.

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?

Single sentence with zero waste. Front-loaded with the verb 'Update' and immediately conveys the resource and actions. Every part earns its place.

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 mutation tool with 6 parameters and no output schema, the description covers the core purpose but lacks details on return value, error conditions, or prerequisites. It is minimally adequate but incomplete for an agent to understand all implications of invocation.

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?

Description maps human-readable actions (enable/disable, pin/unpin, change interval/time) to schema parameters, adding meaning beyond the schema's type/descriptions. For example, 'enable/disable' corresponds to 'enabled' boolean; 'pin/unpin' to 'pinned'. This adds value, though not all parameters (like device_id) are explained in the description.

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 the verb 'update' and resource 'installation' and enumerates specific operations (enable/disable, pin/unpin, change render interval and display time). This distinguishes it from sibling tools like update_device (which updates device settings) and list_installations (which lists installations).

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?

No explicit when-to-use or alternatives are provided. The description lists what can be changed, but does not mention prerequisites (e.g., need installation_id from list_installations) or when not to use this tool (e.g., vs. delete_installation). Implied usage is clear but lacks structured guidance.

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