Get_ATC_ResultList

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

No annotations are provided, so the description must convey behavioral traits. It indicates a read operation ('retrieve') but does not mention side effects, permissions, rate limits, or pagination details beyond maxResults. Sufficient but minimal.

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?

Extremely concise: two sentences with front-loaded purpose. Every word adds value, no 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?

Covers core functionality and key parameters. However, with no output schema and no annotations, it could describe the return format or behavior (e.g., 'returns a list of result IDs'). Adequate for a simple list retrieval but not overly complete.

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 the existing parameter descriptions are comprehensive. The description adds little beyond what is in the schema (e.g., 'Filter by period...' is already covered). Baseline 3 is appropriate.

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 it retrieves the ATC result list, with specific scopes and filters. However, it does not explicitly differentiate from the sibling Get_ATC_ResultDetail tool, which likely provides individual result details.

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?

Provides guidance on using scope=central vs local, and lists filters. However, it lacks explicit when-to-use vs when-not-to-use compared to sibling tools, and no prerequisites or context are mentioned.

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