se_search

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

Annotations already classify the tool as readOnlyHint, idempotentHint, and destructiveHint false. Description adds that the search is over title and full text, which is behavioral context, but adds little beyond annotations.

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?

Single, concise sentence that front-loads the action and resource. Every word contributes to understanding.

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 only one required parameter, clear annotations, and an output schema, the description covers the tool's functionality sufficiently for an agent to correctly 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 coverage is 100% and provides an example. Description enhances parameter meaning by specifying that 'query' searches both title and full text, adding value beyond 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?

Description clearly states it searches Swedish statutes (a specific resource) by free text in title and full text. It distinguishes from sibling tools 'se_get_act' and 'se_get_text' which likely retrieve specific acts, making purpose 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?

Description implies usage for searching statutes, but does not explicitly state when to use this tool vs siblings or when not to use it. It provides clear context for use.

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