get_freshness

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

Discloses that coverage is not full-market and bounded, adding context beyond the name. However, lacks mention of read-only nature, authentication requirements, or error behavior. Annotations are absent, so description carries full burden but falls short.

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?

Two concise sentences with no fluff. First sentence delivers primary purpose, second adds important caveats. Efficient and well-structured.

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 no output schema, description does not describe return format or example output. Also missing parameter guidance. Only covers purpose and a single caveat, leaving significant gaps for agent decision-making.

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 0% and description does not mention the single parameter (freshness_window_hours). No additional meaning provided beyond what the schema already states.

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 states it returns freshness status for a specific universe (Headless Records watched ticker universe) and distinguishes from siblings by focusing on coverage status rather than insider activity or filing provenance.

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?

No guidance on when to use this tool vs alternatives (assess_insider_activity, get_filing_provenance). No explicit usage conditions or when-not-to-use.

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