get_news_categories

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is 'free, no credits', which is helpful for cost awareness. It also implies a read-only operation ('Reference data'). Missing details about caching or real-time behavior, but acceptable for a simple reference tool.

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, well-structured sentence that conveys all essential information: purpose, output, usage context, and cost. Every word earns its place with no redundancy.

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 no parameters and no output schema, the tool is simple. The description covers its purpose and usage adequately. It does not describe output format (e.g., codes structure), but for a reference list tool, this is sufficient. A minor gap is lack of pagination or limit info, but not critical.

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 no parameters (schema coverage 100% with zero params), so the description does not need to document parameters. The description adds value by explaining the output's purpose (filter values). Baseline 4 is appropriate.

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 tool's purpose: 'get all news category codes for use as filter values in news searches'. It specifies the verb 'get' and the resource 'news category codes', and distinguishes itself from sibling tools like 'search_news' by indicating it provides reference data for filters.

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 explains when to use the tool: 'for use as filter values in news searches'. It implies usage before search_news, but does not explicitly mention when not to use it or provide alternatives. However, the context of sibling tools makes it clear.

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