Find a Bolagsanalys parameter

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description reinforces 'Read-only' and 'never writes'. It adds useful context like 'Shared reference data', which explains the data's nature beyond the annotation. No contradictions.

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 three sentences, front-loaded with 'Read-only' and the core purpose. Every sentence adds value: purpose, workflow, and example. No fluff or redundancy.

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 the tool has an output schema and 100% schema coverage, the description does not need to repeat return structure. It provides complete context for how the tool fits into the broader API workflow, which is sufficient for an agent to select and invoke it.

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 100%, so parameters are already well-documented. The description adds value with a concrete example (nameContains 'revenue', group 'Income statement') that demonstrates how to combine parameters, elevating it above the schema baseline.

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 states a specific verb ('Discover') and resource ('financial parameter'), and names the specific fields returned (code, English name, group, description). It distinguishes itself from siblings by explicitly connecting to `bolagsanalys_get_data`, making its role in the workflow unambiguous.

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?

Provides clear when-to-use guidance: 'Use this to resolve the `parameterCode` you then pass to `bolagsanalys_get_data`'. It also references `bolagsanalys_list_companies` for obtaining a `companyId`, establishing a workflow. It does not explicitly mention when not to use it, but the positive use case is strong enough.

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