Collect and rank observed X posts

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

Annotations already declare readOnlyHint/destructiveHint/openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: in-memory merging, deduplication, rejection of stale/unrelated posts, and the important caveat that it 'does not fetch or independently authenticate host-supplied text' — a trust boundary the agent needs. It does not cover error/partial-success handling for rejected captures.

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?

Four tight sentences, front-loaded with the precondition, then behavior, then constraint, then the trust caveat. No filler, though the final sentence could be folded into the behavior sentence without loss.

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?

With no output schema, the description usefully discloses the return shape ('returns dates and source links') and the processing pipeline, which is adequate for a two-parameter ingestion tool. The main gap is that the fairly complex nested capture structure is left entirely to the schema.

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% and the nested capture/post objects (including the state enum values login_required, rate_limited, challenge, empty, unrecognized) are entirely undocumented. The description adds only a partial hint that captures must reference the plan's search URLs; it never explains what searchId refers to or what the capture fields mean.

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 and resource ('submit exact captured posts') plus the downstream effects (merges, dedupes, filters, returns dates and links). It also positions itself in the workflow relative to x_search_topic ('after x_search_topic and browser reading'), so an agent can distinguish it from the sibling search tool without opening a schema.

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?

Gives a clear precondition and sequencing ('After x_search_topic and browser reading') plus a hard constraint ('Captures must use the plan's search URLs'). It stops short of naming when-not-to-use or explicitly contrasting with x_get_status, so it is strong but not fully exhaustive.

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