si_comp_get_merger

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

Description indicates a retrieval operation but does not disclose any behavioral traits such as error handling, authentication requirements, or rate limits. Since annotations are absent, more detail would be beneficial, but the simplicity of a 'get' tool mitigates the gap.

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 sentence, no wasted words, front-loaded with purpose. Very concise.

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 tool with one parameter and no output schema, the description is mostly adequate but lacks mention of what is returned or any usage context. It does not cover potential errors or alternative tools, leaving some 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?

Schema coverage is 100%, so baseline is 3. The description provides an example ('306-K-1/2023') that adds modest value beyond the schema description. No other parameter details are missing.

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 verb 'Get' and resource 'specific AVK merger control decision' with an example case number. While it distinguishes from siblings implicitly by specifying 'by case number', it does not explicitly differentiate from si_comp_search_mergers or si_comp_get_decision.

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?

No guidance on when to use this tool versus alternatives like si_comp_search_mergers or si_comp_get_decision. The context is implied by the case number parameter but no explicit when/when-not advice is given.

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