set_cpu_late_limit_permille

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

No annotations are provided, so the description must fully disclose behavioral traits. It lacks details on side effects, persistence, immediate effect, or impact on system performance. It only states it 'controls scheduler behaviour', which is vague.

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 concise, with purpose stated upfront and extra information (requirement, range) appended. It is efficient but slightly cluttered by the inline range: could benefit from clearer separation.

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 simplicity of the tool (one parameter, no output schema, no annotations), the description covers the essentials: purpose, range, default, and requirement. However, it lacks explanation of what 'late tasks' are or when to modify this setting, making it adequate but not thorough.

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 a minimal description. The tool description adds meaningful context: the parameter is a 'CPU late task limit in permille', the range and default are provided, and the required compilation flag is noted. This adds value beyond the schema's repetition of the name and type.

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 it sets cpu_late_limit_permille, a CPU late task limit in permille, and explains it controls scheduler behaviour when tasks are running late. This is a specific verb-resource pair that distinguishes it from its getter sibling.

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?

The description includes a required compilation flag (USE_LATE_TASK_STATISTICS) and the parameter range/default, but does not provide explicit guidance on when to use this tool versus alternatives or under what conditions to adjust the limit. Usage is implied but not elaborated.

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