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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds genuine extra context: the 'hosted hot window' scope constraint, the enumerated return payload (settlement date, quantity, issuer label, price field, source file, snapshot hash, provenance), and an interpretation disclaimer about long vs short sales. That is real value beyond the annotations, though no rate-limit or freshness caveats are given.

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?

Three sentences, zero waste: capability and scope first, payload enumeration second, usage examples and disclaimer last. Nothing is redundant with the schema or annotations.

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?

There is no output schema, but the description compensates by enumerating the returned fields, and the input schema is fully described. The scope ('hosted hot window') is noted, though finer detail on the window's boundaries or error behavior is absent — a minor gap for a single-record lookup.

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 100%, so all three parameters are already documented in the schema, including the as_of format and the ticker pattern. The description only restates 'one exact ticker' and 'optionally as of a date', adding no syntax or constraints beyond what the schema delivers — the baseline 3 applies.

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 ('Return the latest published official SEC fails-to-deliver balance for one exact ticker'), with 'latest' and 'one exact ticker' distinguishing it from sec_ftd_history, sec_ftd_top, and sec_ftd_search_securities. An agent can tell what it does and how it differs from siblings without opening any 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?

Provides two concrete invocation examples ('latest reported FTD balance for GME', 'most recent AMC fail balance by June 30?') that show the intended use case clearly. It does not, however, explicitly state when NOT to use it or name the alternative sibling (sec_ftd_search_securities appears only in the schema, not the description).

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