moneycontrol_get_news

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds context on return format (markdown or json), the structure of returned articles, and the empty response message, enhancing transparency without contradiction.

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 (three paragraphs) with clear sections (Args and Returns). It is front-loaded with the main purpose and uses bullet-like structure to list parameters, making it easy to scan.

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 four parameters, detailed schema descriptions, and an output schema, the description covers all essential aspects: query vs category behavior, limit range, response format, and return format. It is complete for an agent to use 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 description explains the meaning and interaction of 'query' and 'category', and mentions 'limit' and 'response_format'. Although the input schema provides detailed descriptions for nested parameters, the tool description adds practical usage context and the relationship between parameters.

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 current Moneycontrol news headlines for a topic, stock, or category.' It uses a specific verb and resource, and the examples distinguish it from sibling tools like moneycontrol_get_quote or moneycontrol_search.

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 'query' vs 'category' and the default category. It provides clear internal usage context but does not explicitly tell when to avoid this tool in favor of siblings, though the purpose is distinct enough.

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