setup_status

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

With no annotations, the description fully covers what the tool returns: API key state, data counts, profile, next steps, capabilities, and analyst_context. It also explains how to treat capabilities as a hard gate, preventing fabrication.

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?

Concise yet comprehensive single paragraph. Front-loaded with purpose and usage, followed by return values and critical instructions. No wasted 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?

Given zero parameters and no output schema, the description provides all necessary context: purpose, when to call, what it returns, and how to interpret results. Complete for the tool's role.

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?

No parameters exist, so baseline is 4. The description adds value by detailing the return fields, which compensates for missing output 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?

Clearly identifies as a one-shot setup diagnostic tool. Distinguishes from sibling tools like add_balance or show_txns which operate on specific data, while this tool checks data availability and capabilities.

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?

Explicitly instructs to call at the start of every conversation and any time unsure of data availability. Provides clear context for use without needing exclusion criteria.

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