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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the time window and aggregation level, but does not state whether this is a read-only analysis, whether it queries live or cached data, what reliability means, or what the response contains. For an unannotated tool this is a notable gap.

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 a single front-loaded sentence with no filler: it names the metric, the grouping, and the time window. It is appropriately compact, though its brevity leaves surrounding context to be supplied elsewhere.

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 one-parameter tool with no output schema and no annotations, the description leaves important context unstated: what values capability should take, how the result is presented, and how this tool relates to its siblings. An agent could guess, but the definition does not give enough to call it with confidence.

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 only parameter 'capability' has no schema description, no enum, and 0% documentation coverage; the description's 'per tool' phrasing hints that capability names a tool but gives no format, accepted values, or example. The description only partially compensates for the missing schema semantics.

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 identifies the resource (tool reliability) and the scope (last 7 days, per tool), which distinguishes it in subject matter from siblings like thruact_act or thruact_call. However, it lacks an explicit present-tense verb such as 'returns' or 'lists,' and it does not explicitly differentiate itself from sibling tools, so it falls 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?

There is no guidance about when to choose thruact_iq over thruact_compare or thruact_discover, and no mention of alternatives, prerequisites, or exclusions. The agent is left to infer usage entirely from the tool name and the one-line description.

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