Product Brain Snapshot

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds that blocks are empty when sources aren't flowing and that time-windowed sections honor the `window` parameter. No contradictions.

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?

Description is moderately sized but every sentence contributes value. It is well-structured, starting with the purpose, then detailing return content, then usage guidance. Could be slightly tighter but effective.

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 no output schema, the description adequately explains the return structure (JSON with blocks) and handles both parameters. It covers edge cases (empty blocks) and dependencies (window). Sufficient for a single-call tool.

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 both parameters already described. The description adds minimal extra meaning: it explains which sections the window applies to and that product_id defaults to primary product. Baseline 3 is appropriate.

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 uses specific verbs ('get a grounded snapshot') and clearly states it returns revenue, accounts, analytics, features, customer signals, and work counts. It distinguishes from sibling tools by advising to 'start here to ground, then go deeper with dedicated list_* reads.'

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 tells when to use this tool ('start here to ground') and directs to alternatives ('go deeper with dedicated list_* reads and analytics tools'). Also notes single call, no pagination, and optional product_id.

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