se_fin_get_regulation

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Get' (implying read-only) and does not mention any side effects, permissions, or return characteristics. For a tool with no annotations, this is insufficient to guide safe invocation.

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 a single succinct sentence followed by examples, with no unnecessary words. It front-loads the core purpose immediately.

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 only two simple parameters and no output schema, the description is largely complete. It explains the input format and the tool's function. However, it could briefly note that the operation is read-only, especially since no annotations are present.

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%, so the baseline is 3. The description adds example reference formats, which provides context beyond the schema's brief descriptions, but does not significantly deepen understanding of the parameters or their constraints.

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 that the tool retrieves a specific Swedish financial regulation provision by sourcebook and reference, using a specific verb ('Get') and resource ('regulation provision'). It distinguishes from sibling tools like 'se_fin_search_regulations' (search) and 'se_fin_list_sourcebooks' (list) by focusing on exact references, and provides concrete reference examples.

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 when you have an exact reference and sourcebook, but does not explicitly state when to use this tool versus alternatives like search or list tools. No exclusions or prerequisites are mentioned, leaving the AI agent to infer the appropriate context.

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