get_tpa_low_always

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

No annotations provided, so description carries the burden. It discloses the possible values (OFF/ON), data type (UINT8), and default (OFF), which provides useful behavioral context for a getter. However, it does not explicitly state that the operation is read-only or non-destructive, though 'Get' implies it.

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?

Single dense sentence that front-loads the tool's purpose and packs the value explanations, type, and default. No wasted words; every part of the description earns its place.

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 provides the type and default, and explains the possible values. It could explicitly state that it returns the current setting, but overall it covers the essential information for a simple getter 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?

No parameters exist, so baseline is 4 per rubric. The description adds no parameter-specific information, but schema coverage is 100% trivially. The description does explain the meaning of the values, which aids understanding of what the tool returns.

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 explicitly states the tool gets the 'tpa_low_always' setting and explains the meaning of OFF and ON values. It clearly identifies the specific resource and adds value by defining the parameter's effect. Among many sibling get tools, this description uniquely defines what this tool retrieves.

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 on when to use this tool versus alternatives (e.g., set_tpa_low_always or other TPA-related tools). The description does not provide context about when this read is appropriate or how it relates to other configuration tools.

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