Get Bolagsanalys quarterly figures

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

Despite annotations already declaring readOnlyHint and openWorldHint, the description adds valuable behavioral context: quarter bounds are packed ids (e.g., '2025Q1') and are NOT calendar dates, every row retains companyId and parameterCode, and the tool never writes. This goes well beyond the annotations to clarify potential pitfalls.

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?

The description is well-structured and front-loaded with the core purpose ('Read-only. Fetch quarterly figures for one company'). It then provides necessary details in a logical order without superfluous content. Every sentence adds value, and the length is appropriate given the tool's complexity.

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 a rich output schema and full schema descriptions, the description focuses on usage context rather than return values. It covers prerequisites, optional narrowing, the packed quarter format, and the read-only nature. It is complete for the tool's complexity and offers clear guidance to an agent.

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?

The schema description coverage is 100%, so the baseline is 3. The description adds extra meaning by explaining the packed quarter format in detail, giving a concrete example (companyId 'SE-VOLV-B', parameterCode 'REV', fromDate '2024Q1', toDate '2025Q4'), and clarifying that quarterId, fromDate, and toDate are quarters, not dates. This enhances the schema's parameter descriptions.

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 fetches quarterly figures for one company, with optional narrowing by parameter and quarter range. It specifies the verb (fetch), resource (quarterly figures), and scope (one company), and distinguishes itself from related tools by referencing prerequisites like companyId and parameterCode sourced from sibling tools.

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 provides clear context on when to use the tool (when you have a companyId from bolagsanalys_list_companies) and explains the source of required IDs. However, it does not explicitly mention when not to use it or name alternative tools such as bolagsanalys_search_data, so it stops short of full exclusions.

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