get_news

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

Without annotations, the description transparently discloses the lazy loading behavior and context window safety considerations. It explains that fetch_body=False returns only headlines and summaries, and that fetch_body=True fetches full text markdown, which is essential for understanding the tool's impact on context.

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 concise and well-structured, with a clear header and bullet points for the context window safety section. Every sentence adds necessary information without 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 the parameter count (4), full schema coverage, and existence of an output schema, the description is complete. It covers the key lazy loading behavior and user guidance, leaving the output details to the output schema.

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?

All parameters have schema descriptions (100% coverage), but the description adds value by explaining the recommended usage patterns for fetch_body and limit, including the lazy loading rationale. This goes beyond the schema to guide effective use.

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 'Get recent news articles and optional full text markdown for a TradingView symbol.' It specifies the resource (news articles) and action (get), and mentions the optional full text, making it distinct from sibling tools like get_documents.

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 explicit usage guidance on context window safety, recommending default fetch_body=False and suggesting fetching full text with fetch_body=True and a small limit. This tells when and how to use the tool efficiently, though it does not directly compare with sibling tools.

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