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

Discloses that content is split by heading to return relevant paragraphs, advises to cite url, and notes that shop terms do not override Finnish law. Annotations are consistent and description adds value beyond them.

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?

Well-structured with Args, Returns, and Notes sections. Front-loaded with purpose. Every sentence adds necessary information without 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 2 simple parameters, an output schema described in Returns, and annotations, the description provides all needed context including behavior, limitations, and guidance. No gaps.

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?

Input schema covers both parameters with descriptions, and the description adds concrete examples (e.g., 'palautus', 'toimitusaika') and explains behavior when query is empty. Schema coverage is 100% but description enriches usage.

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?

Clearly states the tool searches Okun Koneosa's shop policies and FAQs. Lists specific topics (delivery, privacy, returns, etc.) and distinguishes from sibling tools like search_catalog which handles products.

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?

Explicitly says 'Use this instead of guessing when the customer asks about delivery times, shipping costs, returns, warranty or how their data is handled.' Provides concrete usage context and alternatives.

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