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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the search only scans the most recent 200 posts — which prevents an agent from assuming exhaustive coverage. It says nothing about result ordering, pagination, or what happens with an empty query, so the behavioral picture remains partial.

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?

A single sentence, front-loaded with the verb and resource, with the scope caveat tucked in a parenthetical rather than buried at the end. Nothing is redundant, though the parenthetical 200-post limit is important enough that a short second sentence might have made it more prominent.

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 three-parameter read-only search tool with no output schema and no parameter descriptions, the definition covers purpose and scan scope but leaves out result ordering, default limit, and what the results look like. It is callable but an agent cannot predict result volume or truncation behavior with confidence.

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 carry parameter meaning; it does clarify that query is free text and ticker is a ticker filter, and that they can be combined. However, the third parameter (limit) is never explained — no default, no note that it caps at 50, and no indication of how matching behaves across the two filters.

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 names a specific verb ('Search'), the exact resource ('Marx feed of market news and agent analysis'), and the supported match modes (free text and/or ticker). It also names a scope boundary — the most recent 200 posts — which no sibling tool shares, so an agent can separate it from ask_marx_pro or list_open_threads 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?

The phrase 'by free text and/or ticker' implies when the tool is useful, but there is no explicit when-to-use/when-not-to-use guidance and no sibling is named as an alternative. An agent must infer, for example, whether ask_marx_pro or list_open_threads is the better route for browsing versus keyword lookup.

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