get_finances

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

No annotations are present, yet the description fails to disclose behavioral traits beyond the data source scope. It omits auth requirements, rate limits, response format, or whether results are paginated. For a read tool, safety is assumed but not confirmed.

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, well-structured sentence with all essential information. No redundancy or filler. Front-loaded with the verb and resource.

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 3 parameters and no output schema, the description provides some context (data sources, time range) but lacks detail on output structure, default behavior, and edge cases. Adequate for a simple retrieval but not fully comprehensive.

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% with baseline at 3. The description adds context (data sources and years) but does not elaborate on parameter semantics beyond what the schema provides. The 'extended' parameter remains undefined.

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 the tool retrieves financial statements of Russian organizations using OGRN or INN, specifying data sources and date range. This distinguishes it from sibling tools focused on other entity details like bank, company, or entrepreneur.

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 usage by specifying input identifiers but does not contrast with alternative tools or state when to use this over others. No explicit when-not-to-use guidance is provided.

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