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

With no annotations, the description carries the full burden. It discloses that it is facts-only, not investment advice, and explicitly states the cost ($0.02 per call) and that failed/empty calls are free. It also reveals the comparison behavior (vs prior window) and the keyword topic flags. It does not mention rate limits or auth requirements beyond the payment key, but the cost and failure disclosure is strong.

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 dense but well-structured: it front-loads the core function, then lists outputs, then adds caveats and cost. Every sentence earns its place, and the cost/failure note is valuable for an agent deciding whether to invoke.

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?

For a tool with no output schema, the description does a good job of explaining what the agent will get: post volume, top posts, active accounts, and topic flags. It also covers cost and failure semantics. It lacks explicit return format details (e.g., JSON shape), but the enumerated outputs are sufficient for an agent to understand the tool's purpose. The absence of an output schema is partially compensated by the detailed output list.

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 the schema already documents both parameters. The description adds context for the ticker parameter by saying 'one US stock ticker' and implies the window parameter via 'prior window', but it does not add syntax details beyond the schema. 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 states a specific verb ('X/Twitter activity for one US stock ticker') and enumerates the exact outputs: post volume vs prior window, top posts, most active accounts, and keyword topic flags. It clearly distinguishes itself from siblings like x_search, x_digest, and x_profile by focusing on a single ticker's activity summary rather than general search or profile 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?

The description implies when to use this tool: when you need X/Twitter activity for a single US stock ticker, including volume comparisons and topic flags. It does not explicitly name alternatives or exclusions, but the sibling list and the specific scope ('one US stock ticker') provide clear context. It also states cost and failure behavior, which helps an agent decide whether to call it.

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