mirror_news

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

With no annotations provided, the description carries the full burden. It discloses that the data is 'fresh' and comes from a 'public News RSS feed', which is useful. However, it does not describe the return format, number of items, or any pagination behavior. The description adds some context but lacks deeper behavioral details that would be expected without annotations.

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 extremely concise, with two short sentences. It front-loads the action ('Get Mirror top stories') and provides a brief clarification. There is no unnecessary information, making it appropriately sized and well-structured.

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?

The tool has no output schema, so the description should explain what the agent can expect from the return value. While it states it returns 'top stories' from an RSS feed, it does not describe the structure or content of the returned data (e.g., titles, links, timestamps). For a simple feed tool, this is a minor gap, but given no output schema, a bit more detail would improve completeness.

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?

The tool has zero parameters, so the input schema is empty. The description does not need to explain parameter semantics. The baseline for 0 parameters is 4, and there is no additional information needed.

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 clearly states the verb 'Get' and the resource 'Mirror top stories', and specifies the source as 'public News RSS feed'. It distinguishes from siblings like mirror_article or mirror_author by focusing on top stories, but does not explicitly differentiate from mirror_headlines, which could overlap. The purpose is clear but lacks explicit sibling differentiation.

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 description provides no guidance on when to use this tool versus alternatives like mirror_headlines or mirror_sections. It does not mention any conditions, exclusions, or alternative tools. There is no contextual information to help an agent decide between this and similar Mirror tools.

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