hs4.admin.cameras.config.delete

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

With no annotations, the description must disclose behavioral traits. It only says 'Delete', but does not mention that this is a mutating admin operation, the need for confirm or maintenanceWindowId, or what happens on deletion (e.g., irreversible? cascading effects?). The description is insufficient for safe autonomous invocation.

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 concise sentence, which is efficient but lacks informative structure. There is no wasted text, but it also fails to leverage the space to add context; front-loading is minimal.

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?

The tool has 10 parameters, two required, and is an admin mutation with no output schema. The description provides none of the operational context needed (e.g., dry-run capability, risk levels, change-ticket requirements). It is too brief to enable correct use in complex workflows.

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 high (90%), so the schema already explains most parameters. The description adds no additional meaning beyond the schema, but that is acceptable given the coverage; thus baseline score 3 is appropriate.

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 action 'Delete' and the resource 'camera config', making the primary purpose evident. However, it does not distinguish this from sibling tools like update or create, missing an opportunity to reduce ambiguity.

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 guidance is provided on when to use this tool versus alternatives (e.g., update or disable), nor are prerequisites or recommended scenarios mentioned. The description lacks usage context entirely.

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