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

With readOnlyHint/openWorldHint/destructiveHint already covering the safety profile, the description adds real behavioral context: newest-first ordering, contents of each wire, refresh cadence ('several times per trading day'), and archive linkage. It stops short of auth or rate-limit details, so not a full 5.

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?

Front-loaded with the two-wire split and dense with specifics; the archive and refresh sentences are short and earn their place. Slightly long overall but no filler.

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?

No output schema exists, so the description carries the return-content burden and does so by describing what each wire contains (calls, price-target moves, consensus EPS comparison, forward calendar). Missing only edge cases such as what an empty wire or invalid ticker returns.

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 coverage is 100%, so baseline is 3, but the description adds semantic meaning to the wire enum beyond 'Which wire (default: analyst)' by spelling out exactly what data each value surfaces. limit and ticker are left to 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?

States a specific verb+resource ('two US wires') and immediately disambiguates the two modes: wire=analyst is sell-side calls, wire=earnings is prints vs consensus. An agent can tell exactly what this returns without opening the schema.

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?

The description clearly explains what each of the two wires delivers, which is the main selection decision for this tool. It gives clear context but no explicit when-not guidance or named alternatives among siblings like get_tape or get_latest_view.

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