get_scheduler_relax_rx

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

No annotations provided. Description adds value by specifying the value type (UINT16), range (0–500), and default (25), but does not explicitly state it is a read-only operation, 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?

Extremely concise and well-structured: one sentence plus bracket info. Every part is necessary and front-loaded.

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 simple get tool with no parameters and no output schema, the description adequately covers purpose, value type, range, and default. Could add more context on when to adjust this value, but sufficient.

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 in schema. Description adds meaning with value type and constraints, which is helpful. Baseline for 0 parameters is 4.

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 'Get scheduler_relax_rx' and explains it controls how much other tasks can run during RX processing. However, it does not explicitly distinguish from sibling 'get_scheduler_relax_osd' or 'set_scheduler_relax_rx'.

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 like get_scheduler_relax_osd or the set counterpart. The description lacks context on appropriate usage scenarios.

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