camera-set

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Set', implying a mutation, but does not mention side effects, permissions, reversibility, or response format. This is a minimal surface-level statement that does not enrich the agent's understanding of the operation's impact.

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 short sentence with no filler or redundancy. It is front-loaded and easy to parse. However, it is so brief that it borders on under-specification, but it earns a 4 for being concise without being bloated.

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 six parameters and no output schema or annotations, a one-line description is inadequate. It doesn't explain what 'common' means, which properties are relevant, or any constraints. The schema compensates somewhat, but the description fails to provide sufficient operational context for an agent to safely select and invoke the tool.

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?

The input schema provides rich titles and enums for each parameter, but the description adds no additional meaning or context for any of the six parameters. Schema description coverage is 0%, so the description fails to compensate for the schema's low-level definitions. It does not clarify how parameters interact, defaults, or typical usage.

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 'Set common camera data properties' clearly identifies the verb (Set) and resource (camera data properties). It distinguishes from siblings like camera-create (create a new camera) and camera-set_active (set active camera). However, the word 'common' is vague and doesn't specify which properties are included, which could lead to 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 explicit guidance is provided about when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or how it differs from other camera-related tools. The description merely states the action without contextual cues.

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