Entity intelligence

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, providing a solid baseline. The description adds that it returns 'recent stories' and clarifies the entity parameter accepts either a name or an ID, which is helpful beyond 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?

A single, well-structured sentence that front-loads the key action and resource. Every word earns its place; there is no extraneous information.

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?

Despite the tool having three parameters and an output schema, the description is sufficient for a straightforward query tool. It identifies the purpose, resource, and parameter semantics for entity. With output schema existing, return values do not need elaboration. Minor gap: no mention of default ordering or recency window.

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 only 33% (only publishedSince has a description). The description clarifies that the entity parameter can be a 'named TNL entity or entity id', which adds value. However, it does not explain the limit or publishedSince parameters beyond what the schema provides.

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 'Return' and the resource 'recent stories connected to a named TNL entity or entity id'. This distinguishes it from sibling tools like tnl_search_news (full-text search) and tnl_asset_intelligence (asset-level intelligence).

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 tnl_search_news or tnl_latest_news. An agent must infer usage from the name and brief description alone.

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