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

Annotations declare read-only, idempotent and open-world behavior, so safety and side-effect profile are covered. The description adds the critical warning that posts are unverified claims, not news confirmation, which is valuable trust-level context beyond the annotations.

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?

Three sentences with no waste: source, use case, and caveat are front-loaded and each 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?

For a read-only search tool with no output schema, the description covers source, intended use, and evidence quality. It would be stronger with a note on the time window or result cap, but the core calling decision is well supported.

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 0%, so the description must compensate, but it only implies ticker input and recency through 'ticker' and 'recent' without explaining hours, limit, or includeReplies, leaving key parameters undocumented.

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 verb 'Search' and a specific resource 'recent X posts about a ticker', and it distinguishes itself from the sibling social.search_posts by describing the cashtag feed as identical to TWIT.

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 says 'Use this when asking what traders are saying or looking for a possible catalyst', giving a clear scenario for use while the description of the cashtag feed implicitly excludes broader post searches handled by social.search_posts.

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