Get instrument feed

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

Annotations already declare readOnlyHint=true, so description's disclosure of read operation is redundant. It adds that the feed contains 'posts, discussions', providing some behavioral context but not beyond what annotations and schema imply.

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?

Single concise sentence front-loading the purpose with no unnecessary words or structure. Every word 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?

With no output schema, description could clarify typical return structure (e.g., 'list of posts'). However, for a simple read tool with fully documented parameters and annotations, it provides enough context for basic use. Lacks mention of sorting or result count.

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% with clear descriptions for all parameters (instrumentId, take, offset). Description adds no extra semantic meaning beyond restating 'for a specific instrument'. Baseline 3 holds.

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?

Description clearly uses specific verb 'Get' and resource 'social feed (posts, discussions)' scoped to 'a specific instrument', distinguishing it from sibling tools like etoro_get_user_feed (user feed) and etoro_get_candles (price 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?

No guidance on when to use this tool versus alternatives (e.g., etoro_get_user_feed for user-specific feed, or other feed/listing tools). Agent must infer usage from context.

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