search_declarations

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as read-only nature, pagination behavior, or any side effects. The description is too sparse to inform the agent about what happens when the tool is invoked.

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, which is concise but too brief given the tool's complexity (10 parameters). It is front-loaded with the key action, but does not earn its place by adding value beyond the name. An appropriate size would include at least one more sentence for context.

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?

Despite the tool having 10 parameters and many sibling tools, the description lacks any contextual information such as output structure, typical use cases, or differentiation. It is insufficient for an agent to understand when or how to use this tool effectively.

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 the individual parameter descriptions are already available. The tool-level description adds no extra meaning beyond stating the purpose. With full schema coverage, baseline score is 3; description does not improve or degrade.

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 searches declarations of conformity, specifies the regulatory scope (ТР ТС / ТР ЕАЭС), and uses a specific verb 'search' with a distinct resource, differentiating it from sibling tools like search_certificates.

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 provides no guidance on when to use this tool versus alternatives such as search_certificates or search_documents. It does not mention exclusions, prerequisites, or context of use.

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