export_checker_data

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

No annotations are provided, so the description must disclose behavioral traits. It states the output format (CSV) and clarifies profileId semantics. However, it does not specify whether the operation is read-only, has side effects, requires specific permissions, or has rate limits. This is a moderate gap given no annotations.

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 total. The first sentence states the primary action and output format. The second sentence provides critical usage guidance. No redundant or extraneous content. Front-loaded with the core 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?

Given the lack of an output schema, the description should explain what data is included in the CSV rows (e.g., which fields of ad objects). It does not mention pagination, limits, or how to obtain the checkerId. While siblings provide some context, the description leaves gaps for an agent to fully understand what it will receive.

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% with descriptions for all parameters, establishing a baseline of 3. The description adds value by explaining that profileId selects a configuration profile 'as a lens, not a container' and advises against assuming profile 1. This goes beyond the schema's minimal 'path parameter' description.

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 the tool exports ad objects related to a deviance in CSV format. The verb 'Get' and resource 'ad objects of a deviance' are specific. Distinguishes from siblings like 'get_ad_object_by_checker' which handle individual objects or different formats.

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 explicit guidance on selecting the profileId parameter: it's a lens, not a container, and instructs to call get_preferred_profile or get_preferences if the user hasn't specified a profile. This prevents misuse and clearly states when to use this tool vs others for profile selection.

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