Applicable Fixlets

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

With no annotations, the description carries the full behavioral burden, and it does convey that the result is a point-in-time, machine-scoped applicability computation. But it says nothing about read-only safety, permission requirements, result volume/pagination, or how freshness is determined, so the disclosure is only partial for a mutation-free query whose semantics matter.

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?

Two short sentences, front-loaded with the core meaning before the clarifying framing. The API path and the second sentence slightly overlap in restating scope, but nothing is wasted or padded.

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?

An output schema exists, so return values need not be explained, and the single required parameter is schema-documented. What remains missing is routing guidance versus the many similarly-named relevance/query siblings, which keeps it from a 5.

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?

Only one parameter, and the schema already documents computer_id as the 'BigFix computer ID' at 100% coverage. The description adds no extra meaning about how to obtain that ID or what happens if it is unknown, so this sits at the baseline for schema-covered params.

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?

States a specific resource (fixlets/content applicable) scoped to one computer, and the parenthetical API path reinforces it. It also distances itself from relevance-query siblings by framing the answer as 'the patch/compliance question: what BigFix currently considers applicable to that machine.' It does not explicitly name the sibling it differs from, so it stops short of a 5.

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 phrase 'This is the patch/compliance question' implies the intended use case, which is better than nothing. However, it never tells the agent when to pick this over close siblings like session_relevance_query, qna_eval_client_relevance, or find_content, nor does it state prerequisites such as the computer needing to exist or report in.

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