News

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

Goes well beyond the annotations by disclosing pagination (25 per page, newest first), de-duplication of repeated filings, `limit` keeping the first N, and content truncation to `contentChars` (default 500) with EGX disclosures being PDFs. These operational traits are exactly the kind of context annotations cannot carry.

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?

Dense but front-loaded, leading with the core purpose before the conditional branches. Some sentences pack multiple clauses (market fallbacks, truncation, PDFs), slightly straining single-pass readability, but every sentence carries distinct information.

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 partially carries the return burden by naming the `link` field and truncation behavior, and all 6 params are covered. It stops short of describing the article record structure (title, date, source), so an agent knows how to paginate and fetch text but not the full shape of each item.

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 coverage is 100%, so the baseline is 3. The description adds real meaning on top: it clarifies the `symbol`-vs-`market` interaction, that `limit` keeps the first N, and that truncated content should be retrieved via `link`, which the schema fields do not convey on their own.

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 (news and exchange disclosures from Thndr's feed) with ordering (newest first) and scope (one instrument, or market-wide). It clearly distinguishes the symbol-filtered path from the market-wide path, which no sibling tool offers.

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 explains conditional behavior: with `symbol` you get one instrument's news; without it, `market: "us"` yields US news and any other market yields the mixed EGX+US feed. It also flags the UAE no-results edge case and tells the agent to follow `link` for full text.

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