ads_clickru_campaign_drafts_status

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

With no annotations, the description must carry behavioral disclosure. It does note the data is 'locally stored' and that nothing is sent or launched, which is genuinely useful side-effect information, but it is silent on auth/setup prerequisites, whether an active campaign may be absent, and what the response looks like.

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 compact sentences with the resource and scope front-loaded and the no-side-effect caveat immediately after. No filler.

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 no-parameter, no-output-schema status tool, the description gives enough: what entity is listed, that statuses and an active campaign are included, and that nothing is launched. Only the absence of edge cases (e.g., no drafts present) keeps it from a 5.

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?

Zero parameters are defined, so the baseline is 4. There is nothing parameter-related to clarify or omit.

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?

States a specific verb ('Show') and resource ('locally stored Click.ru campaign drafts'), plus what is returned: statuses and the active campaign. The sibling ads_clickru_campaign_draft_set_status is implicitly distinguished by the read-only framing, though it is never named.

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 line 'Drafts are not sent or launched' clarifies that this is a passive inspection tool, but it does not say when to reach for it over ads_clickru_campaign_draft_set_status or any other Click.ru tool. Usage is implied rather than prescribed.

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