atcWorklists

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

Describes compact format, truncation flag, and dependency on runResultId. No annotations provided, so description carries burden; it covers key behaviors but omits auth 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?

Two concise sentences front-loading purpose and format, with efficient filtering guidance. No unnecessary words.

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?

Explains purpose and compact behavior but does not detail response structure or provide context for optional parameters like timestamp or includeExempted. Lacks completeness for a 7-parameter tool with no output schema.

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 covers all 7 parameters with descriptions. The description adds minor context (e.g., runResultId source, filtering advice) but does not significantly enhance understanding beyond the schema.

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 findings of a completed ATC run and mentions filtering by objectName. It distinguishes itself as STEP 3 but does not explicitly contrast with sibling tools like atcCentralResult.

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 context as STEP 3 and advises using objectName for large worklists. However, it does not specify when not to use this tool or mention alternatives.

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