Setell autonomy modes

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

The description adds significant detail beyond annotations: explains the safety floor (FLAG always asks), mode behaviors in different scenarios, and that 'canConfigure' depends on paid plan. This is valuable context beyond the readOnlyHint annotation.

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 paragraph that is front-loaded and informative. Every sentence adds value, though it could be slightly more structured (e.g., bullet points for modes). It is appropriately concise for the complexity.

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 no output schema, the description adequately explains what is returned (modes per action class and canConfigure). It covers the key behavioral aspects, though the exact JSON structure is not provided.

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?

There are no parameters, so the baseline is 4. The description correctly focuses on the return values and behavior, fulfilling the need without parameter documentation.

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 tool shows per-action-class autonomy modes, specifying the action class 'send_quote' and explaining each mode (WATCH, TRUST, AUTO) along with the 'canConfigure' flag. This provides a specific verb+resource and distinguishes from siblings like setell_set_autonomy.

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?

Usage is implied as a read-only getter for checking current autonomy modes before potentially using setell_set_autonomy. However, no explicit when-to-use or when-not-to-use guidance is provided, nor are alternatives mentioned beyond the sibling context.

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