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

With no annotations, the description carries the full burden and does meaningful work: it discloses the $0.02 per-call cost, that it is paid from clink's shop credits, that top-ups are currently paused, and that failed/empty calls are free. It also flags the 'facts only, not investment advice' framing, which matters for a finance tool. It stops short of 5 because return format details, rate limits, and auth requirements beyond the existing key are not 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?

Purpose is front-loaded, the content list uses a tight parenthetical enumeration, and the two trailing sentences (disclaimer, pricing) each carry distinct, non-redundant information. No filler; every sentence earns its place.

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?

There is no output schema and no annotations, so the description must carry both — and it does reasonably well by enumerating the returned content and disclosing cost/billing behavior. What is missing is any note on data freshness/latency or how the ticker and window interact, but for a two-parameter read tool this is close to 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 description coverage is 100%, so both parameters (ticker, window) are already documented, including the 24h/7d enum. The description adds only marginal semantics — 'one US stock ticker' (a US-only constraint not in the schema) and 'vs the prior window'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource and scope: 'X/Twitter activity for one US stock ticker', and enumerates the returned content (post volume vs prior window, top posts, most active accounts, keyword flags). The verb is implicit (activity/aggregation) but the resource is unmistakable. It does not, however, distinguish itself from siblings like x_search or ticker_brief, so it stops short of a 5.

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?

Usage is only implied: the 'one US stock ticker' scope and the social-activity framing tell the agent roughly when this applies, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. x_search for broader X queries, ticker_brief for fundamentals). Adequate but leaves routing to inference.

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