get_blackbox_disable_attitude

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

Description explains the setting's effect (exclude attitude data) but does not disclose the tool's own behavior (e.g., returns current value, no side effects). Annotations absent, so minimal burden but adequate for a simple getter.

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, efficient sentence with appended type/default info. Slightly redundant by repeating tool name, but otherwise concise.

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?

For a param-less getter with no output schema, nearly complete. Informs type and default, but could explicitly state return value (current setting). Minor gap.

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 in schema. Description adds value by stating type (UINT32) and default (OFF), which is useful since schema is empty.

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?

Clearly states the tool retrieves the setting that excludes attitude data from blackbox logs. Distinguishes from siblings like get_blackbox_disable_acc by specifying 'attitude'.

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 on when to use this vs. other getter tools or the corresponding setter. Implied by context but not stated.

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