send_indi_property

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

No annotations are provided, so the description must convey behavioral traits. It implies mutation ('setting elements') but does not disclose side effects, permissions needed, or whether the command is destructive. For a tool that modifies device state, this is insufficient.

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 with no redundancy. It front-loads the action and target. However, it could benefit from slight expansion to improve clarity without becoming verbose.

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 presence of 3 parameters including a nested object, and an output schema, the description is too short. It fails to explain the purpose of the output, provide examples, or cover edge cases. The tool appears to be a write operation but lacks sufficient context.

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%, yet the description only briefly mentions 'property name' and 'elements' without clarifying their meaning or valid values. 'device' is not explained. The description adds minimal value over the raw schema.

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 action ('send a command'), the target ('INDI device'), and the effect ('setting `elements` on its property `name`'). It differentiates from sibling tools which are about listing, starting, stopping, etc. However, it could be more explicit about the relationship between 'command' and 'property'.

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 like list_indi_driver_catalog or start_indi_driver. There is no mention of prerequisites, common use cases, or when not to use the tool.

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