Get X account summary

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

With no annotations, the description explicitly declares read-only behavior, absence of local persistence, and the specific external endpoint. It also hints at alignment with x.com analytics. It omits auth requirements and rate limits, but for a read-only analytics tool the core safety profile is well covered.

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 sentences that are dense with specific details: endpoint, data types, timezone alignment, and side-effect warnings. No filler or redundancy; front-loaded with action and resource.

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?

No output schema exists, so the description should indicate return values; it does so by listing impressions, engagements, totals, and top posts. It also notes timezone alignment. It doesn't mention auth prerequisites or behavior for empty windows, but for a read-only summary with 4 optional params it is reasonably complete.

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 descriptions cover 100% of parameters, so baseline is 3. The description adds contextual meaning for 'days' (calendar-day) and 'topPosts' (top posts), but doesn't directly explain each parameter's syntax or format beyond the 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?

The description clearly states the tool summarizes an X account using GET /2/tweets/analytics, listing specific outputs (impressions, engagements, period totals, top posts). It distinguishes from sibling tools like get_x_post_metrics (post-level) and get_x_account (account details).

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 description gives clear context: read-only, no local DB, aligned with x.com account analytics, but does not explicitly mention when to prefer this over siblings or list alternatives. No exclusions are stated, but the read-only nature is a strong usage signal.

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