List official EQL news

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It only says 'Parse the official EverQuest Legends news index', which implies a read operation, but does not confirm idempotency, potential side effects, authentication needs, or rate limiting. The term 'Parse' could be misinterpreted as a destructive or processing action.

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?

The description is a single concise sentence with no wasted words. However, it sacrifices informativeness for brevity; a slightly longer description could add value without becoming verbose.

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?

Given the tool has one optional parameter, no output schema, and no annotations, the description is insufficient. It does not describe the return format, pagination behavior, or how this tool relates to siblings like 'eql_official_article' (which likely fetches a specific article). An agent needs more context to use it correctly.

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 documentation coverage is 0%, meaning the description adds nothing about the single parameter 'limit'. The schema provides numeric bounds and a default, but the description does not explain how the limit affects results (e.g., number of news items returned) or any formatting constraints.

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 verb 'Parse' is ambiguous; it suggests processing rather than listing. The description states the tool operates on the 'official EverQuest Legends news index', but does not clarify what it returns (e.g., list of news items, summaries, metadata). It distinguishes from sibling 'eql_official_article' (which likely retrieves a single article) only by the resource name.

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 is provided on when to use this tool versus alternatives like 'eql_official_article' or 'eql_source_fetch'. There is no mention of prerequisites, typical use cases, or conditions that would make another tool more appropriate.

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