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

With no annotations, the description must carry behavioral weight. It reveals that results include prices and measured reliability and implies a non-mutating search operation. However, it does not describe output structure, edge cases, or whether any side effects exist beyond the 'search' framing.

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 with no filler. The core purpose and result attributes are front-loaded, and the workflow hint 'Search first, execute second' earns its place by guiding correct usage.

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 two-parameter search tool with no output schema, the description plus schema is largely adequate to invoke correctly. It could be more complete by describing the result format or clarifying what 'measured reliability' means, but the essentials are present.

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 description coverage is 100%, so the baseline is 3. The description maps the job concept to the query parameter but adds no extra syntax, format, or boundary information beyond what the schema already provides for query and limit.

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 states a specific action ('Find capabilities for a job'), names the resource ('capabilities'), and adds distinctive result attributes ('prices and measured reliability'). The phrase 'Search first, execute second' also separates this discovery tool from execution siblings like thruact_act and thruact_call.

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 gives a clear workflow signal: search first, execute second. This tells an agent to use this tool before acting, which distinguishes it from execution-focused siblings. It does not explicitly name alternatives or list when-not-to-use conditions, but the context is clear.

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