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

With no annotations, the description carries the full burden, but it only discloses that the tool is paid, the price, and that it works on Base Mainnet. It does not state whether it is a read-only operation, whether it has side effects, rate limits, or what happens on first call versus retry. The 'not a calibrated probability' caveat is a useful behavioral hint but insufficient.

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 short and includes essential payment/network facts, but it is a single run-on sentence that mixes purpose with transactional details. It front-loads the vague 'engine' phrase but does not organize the information logically; payment info is necessary but secondary to the core function.

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 paid tool with a two-step payment flow (challenge then signed retry), no output schema, and a free-form request object, the description is critically incomplete. It does not explain what the response returns, the payment challenge flow, or how to construct a valid request. The agent would have to rely entirely on the parameter description for the payment flow and guess at the request format.

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 50%, and the description does not compensate for the undocumented 'request' parameter. It never explains what the request object should contain or how to structure it, and it adds no meaning to 'paymentSignature' beyond what the schema already states. The nested object with additionalProperties makes this gap worse.

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 it is a 'research-derived information weighting engine', which gives a general sense of function, but it lacks a specific action verb and does not differentiate it from sibling tools like faber_evidence_quality or faber_event_delta. The caveat about not being a calibrated probability adds some clarity about output semantics.

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 on when to use this tool versus any of the alternatives. The description focuses on payment details and network information but never explains what scenario calls for an information weighting engine or how it relates to the sibling tools.

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