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

Annotations already indicate a safe read-only operation. The description adds meaningful context: it is a paid call with specific pricing, and it deliberately omits raw provider records, which is an important privacy/redaction behavior.

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 compact and front-loaded with the most operationally critical fact, the pricing, before stating the core behavior. No filler is present, though the dense jargon slightly reduces readability.

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?

With one required parameter and no output schema, the description should clarify the expected input and output shape, but it does neither. The pricing and redaction details are useful, but an agent cannot confidently construct a correct call or interpret the return value from this description alone.

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%, and the description does not explain what the required 'horse' string parameter should contain, any format constraints, or how it relates to the Horse Truth read. The description entirely fails to compensate for the missing schema documentation.

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 names a clear action ('Return a structured explanation') and resource ('current derived Horse Truth read'), and adds a distinguishing constraint ('without exposing raw provider records'). It does not explicitly compare itself to siblings like horse_intelligence or horse_snapshot, so it stops short of full differentiation.

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 choose this tool over its siblings or what prerequisite conditions apply. The phrase 'current derived Horse Truth read' implies some stateful dependency, but it is not explained.

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