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

The description adds critical behavioral information regarding authentication that is not present in the annotations. It explicitly states that an API key or wallet token (X-API-Key or Authorization: Bearer) is required for the tool to function.

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 definition is highly efficient, using two sentences to convey the 'why' (usage), the 'how' (5 factors), and the 'how-to-authenticate' (API key requirements) without any wasted words.

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?

Given the tool is a lookup function with minimal input and no output schema, the description is maximally complete. It addresses the required input type (article ID) and essential external requirements (API key), leaving no major operational gap for the agent.

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?

Since the input schema only defines a simple UUID, the description provides the necessary semantic context by explaining that the tool operates on 'one article.' It also elaborates on the complex 5-factor scoring mechanism, which is not captured in the schema.

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 defines the tool's purpose as calculating a 5-factor confidence score for a single article. By listing the factors (source tier, freshness, etc.), it differentiates this function from broader sibling tools like search or sentiment analysis.

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?

It provides strong usage guidelines by instructing the agent to use the tool 'BEFORE treating a headline as tradeable or citing it as fact.' This establishes a clear context for when the tool is necessary and when it is not.

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