thruk_perfdata_near_threshold

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as whether the operation is read-only, what scoping is applied (hosts vs services), or potential performance impact. The description is too brief to inform the agent beyond the basic function.

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 very short but lacks structure and clarity. It uses unconventional formatting (double backticks and percent signs) which may hinder readability. While concise, it sacrifices completeness and effective communication.

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 tool has four parameters, no output schema, and no annotations, the description is insufficient. It does not explain return format, pagination, performance implications, or how the results relate to the filter parameter. A more comprehensive description is needed for the agent to use this tool correctly.

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?

The schema covers all four parameters with detailed descriptions (coverage 100%). The tool description only repeats the 'within_percent' parameter name without adding new meaning. Per the guidance, baseline 3 is appropriate since the schema does the heavy lifting.

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 returns metrics near threshold values, referencing the 'within_percent' parameter. It is specific enough and distinguishes this tool from general perfdata retrieval tools like 'thruk_perfdata_snapshot'. However, the use of backticks and double percent signs may be confusing.

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 is provided on when to use this tool versus alternatives such as 'thruk_perfdata_snapshot' or 'thruk_get_perfdata'. The description lacks context on prerequisites, limitations, or recommended use cases.

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