get_account_condition

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

With no annotations, the description bears full responsibility. It states 'Facts, never a verdict,' indicating the tool returns objective data rather than interpretations, but it does not mention potential issues like rate limits, errors, or data availability, leaving some behavioral aspects undisclosed.

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?

The description is compact, using two sentences to convey the tool's purpose, content, and usage guidance. It is well-structured and free of fluff.

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?

It includes the output fields and a practical usage note. However, it does not elaborate on the meaning of 'active_ads_recent' or potential edge cases (e.g., missing data), but overall it leaves the agent with enough context to use the tool effectively.

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?

The tool has no parameters, so the description does not need to explain them. Since the schema is empty, the description's mention of output fields is sufficient and adds no unnecessary param-related content.

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 that the tool retrieves the brand's current operating condition, listing the exact fields (state, last_active, days_since_active, active_ads_recent) and the possible states. It differentiates from sibling tools by focusing on account condition/recency rather than ad performance or competitor data.

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?

It explicitly advises to 'check this before advising' and explains why a dark account requires a different first message than a live one, giving clear situational guidance for when to use this tool.

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