get_news_item

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

With no annotations, the description carries the full burden. 'Show' implies a read-only operation and 'full text and comments' indicates what is returned, but it does not mention permissions, error behavior, or any side effects. This is adequate for a read tool but lacks additional behavioral detail.

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 two sentences, front-loaded with the purpose, and contains no filler. Each sentence contributes either to understanding what the tool does or how to supply the required argument.

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?

For a simple read tool with one required parameter and an output schema, the description covers the essential purpose and argument. It could mention potential caveats like not found errors, but the output schema handles return structure, so this is fairly complete.

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 0%, so the description must compensate. It explains news_id as 'news item ID' and tells the user to get it via list_news, adding meaning beyond the bare schema type. This sufficiently covers the single parameter.

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 uses a specific verb ('Show') and resource ('a news item's full text and comments'), clearly distinguishing this from sibling tools like list_news, create_news, update_news, and delete_news. It states exactly what the tool retrieves.

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 advises using list_news to obtain the news_id, which gives context for when to use this tool versus list_news. It does not explicitly exclude other use cases, but the instruction is clear enough for a simple getter.

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