get_recent_annual_reports

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

With no annotations, the description must fully disclose behavior. It notes the source and type of data (post-issuance updated obligor financials), adding context beyond the tool name. However, it does not mention safety (read-only), rate limits, or response format, leaving gaps.

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?

A single sentence that is front-loaded with the core purpose and includes specific financial terms, making it efficient and easy to scan. Every word earns its place.

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?

For a simple list retrieval tool without an output schema, the description provides reasonable context about what the reports contain. However, it lacks details on pagination, default limit, or how results are ordered, and does not compensate for the missing parameter explanations.

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%, so the description must explain parameters. It does not mention 'limit' or 'issuer_contains' at all. The parameter names are somewhat self-explanatory, but the description adds no semantic value beyond 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?

The description clearly states it retrieves recent issuer annual financial reports for post-issuance obligor financials, using specific financial terms (revenue, operating income, debt-service coverage). This distinguishes it from sibling tools like get_recent_continuing_disclosures or get_recent_official_statements.

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 implies use for obtaining updated financials but provides no explicit guidance on when to use this versus similar tools (e.g., get_recent_continuing_disclosures). No alternatives or exclusions are mentioned, which is a gap given the number of sibling tools.

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