news_category

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Get news'. It does not state whether the operation is read-only (though implied), any pagination behavior, return format, or rate limits. The brevity leaves key behavioral aspects undisclosed.

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, minimal sentence with no excess words. It is front-loaded with the core action and resource, and every word earns its place. Nothing is superfluous.

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 presence of many sibling news tools (news_ticker, news_country, news_general), the description is insufficiently contextual. It does not explain what distinguishes a 'category' from these other news filters, nor does it describe return behavior or use cases. For a tool with no output schema and no annotations, an agent would likely struggle to select 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?

The schema already provides full documentation for the single parameter (category) with a description and example ('business', 'technology'). Since schema coverage is 100%, the tool description adds no additional value beyond what the schema already gives, so the baseline of 3 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 verb (Get) and resource (news for a category), which makes the basic purpose understandable. However, it does not distinguish from sibling news tools like news_ticker, news_country, or news_general, so the agent cannot tell them apart based on the description alone.

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 the many sibling news tools. It does not mention alternatives, exclusions, or any selection criteria. The agent is left to infer that 'category' relates to news topics, but there is no comparison to other news resources.

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