set_pid_profile

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

With no annotations, the description carries full burden. It correctly indicates that the switch is not automatically saved (must call cli_save). However, it omits crucial behavioral traits such as whether the tool requires a connected flight controller, whether it can be called while armed, or the impact on the PID controller during flight. Partial 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?

Two short sentences, no redundant information, front-loaded with the primary action. Every word is necessary.

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 complexity of the flight controller context and many sibling tools, the description is minimal. It does not explain what PID profiles are, how many exist, or the relationship with similar tools like set_rate_profile. However, it does cover the essential action and persistence requirement, making it minimally adequate.

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 coverage is 100% with good parameter description (type, range, 0-based note). The description only repeats '0-indexed' without adding any new meaning, such as what the index represents (profile number) or typical values. The description adds minimal value beyond the 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 states the verb 'Switch' and the resource 'active PID profile', and clarifies the indexing is 0-based. This clearly identifies the tool's action, though it could be more specific about what a PID profile is. Still, it distinguishes from other set tools like set_rate_profile.

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?

Provides a sequential instruction to call cli_save afterwards, which implies that the change is not automatically persisted. However, it does not explain when to use this tool versus alternatives like copy_pid_profile or set_rate_profile, nor does it mention any prerequisites or contexts (e.g., whether flight controller must be disarmed).

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