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

Annotations already cover read-only/idempotent safety, and the description goes well beyond them with substantive data-coverage disclosures: post-2018 originals excluded, reruns aliased, only reviewed labels searchable, caller titles/summaries omitted, opaque clip IDs, and collection links not resolving to a single clip. These are exactly the gotchas an agent needs before interpreting results.

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?

Dense but efficient: the purpose leads, and each subsequent clause carries a distinct data constraint rather than filler. The final sentence about clip IDs and collection links is slightly tangential to a list operation but still earns its place given no output schema exists.

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 no output schema, the description usefully covers return-value quirks, and annotations carry the safety profile. However, for a 3-parameter tool with zero schema coverage it leaves the parameters, defaults, and limit-based pagination entirely unexplained, which is a real gap for correct invocation.

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?

Three parameters (date, year, limit) with 0% schema description coverage, and the description says nothing about any of them — no date format, no interaction between date and year, no limit cap of 20, no default. The passing references to 'date labels' and 'same date' do not document the parameters.

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 (List) and a precisely scoped resource (unique historical Moneytalk recording metadata and canonical collection links), including the deduplication rule for distinct hours on the same date. It does not name search_moneytalk or get_moneytalk_clip, so the agent must infer the boundary from the implied 'searchable labels' phrasing.

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 explains what data is and isn't included (originals after 2018-09-30 excluded, reruns are aliases), but never states when to call this versus search_moneytalk or get_moneytalk_clip. There is no explicit when-to-use or when-not guidance.

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