search_by_regon

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the lookup purpose and does not disclose whether it is read-only, what the response looks like, or any constraints or side effects.

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 sentence that is concise, direct, and free of unnecessary detail. Every word adds value, focusing on the essential purpose.

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?

For a simple one-parameter lookup tool, the description covers the core purpose but lacks information about the return format, error handling, or any usage context. With no output schema, the description should at least hint at what the tool returns upon success.

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 only declares a string property 'regon' with no description. The description compensates by explaining that REGON is a 9- or 14-digit statistical id, which clarifies the expected format and meaning for the single parameter.

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's action ('look up'), the resource ('Polish business entity'), and the specific identifier ('REGON'). It effectively distinguishes this from siblings like search_by_nip and search_by_krs by focusing on the REGON id.

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 the tool is for when you have a REGON, but it doesn't explicitly state when to prefer this over alternatives or mention any exclusions. No guidance on context or when-not-to-use is provided.

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