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 discloses only one behavioral trait: 'No failover.' It does not mention possible side effects, whether the tool can invoke arbitrary actions, how invalid tool ids are handled, or whether this is a read-only operation or can mutate state.

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 extremely short and front-loaded: 'Run one specific tool by id. No failover.' Both clauses carry meaning and there is no wasted text. However, the phrasing is so compressed that some clarity is sacrificed, especially around 'tool by id.'

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 generic tool dispatcher with no annotations, no output schema, and a free-form params object, two sentences are insufficient. The agent does not learn what params contains, what the return value is, what happens on unknown ids, or whether running a tool can have side effects. The missing information is essential for safe invocation.

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 0%, so the description must compensate, but it only clarifies that 'tool' is an id. It does not explain that 'params' is an object passed into the selected tool, what keys it should contain, or how it interacts with the tool. The description adds minimal meaning beyond the parameter names.

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 uses a clear verb and resource: 'Run one specific tool by id.' It communicates that this tool executes one named tool rather than performing some broader orchestration. It doesn't explicitly distinguish itself from siblings, but the 'one specific tool by id' framing is distinctive enough for basic selection.

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 explicit guidance about when to use thruact_call versus any sibling like thruact_act or thruact_proxy. 'No failover' hints at a selection criterion, but the description never names alternatives or explains when failover would be available. An agent would have to infer usage from the name and sibling list.

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