Fetch current Moneycontrol headlines for a chosen news section, returning 25 to 50 stories without publication times.
Get Moneycontrol section headlines. Returns the current headlines of one Moneycontrol news section (25 to 50 stories, without publication times).
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Moneycontrol section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It does reveal the response size range and the absence of publication times, which is useful. However, it does not describe the return structure (whether items include URLs, authors, etc.) or any potential limits/pagination, leaving gaps for an agent.
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, efficient sentence that leads with the verb and resource and packs in the key behavioral details (count range, no publication times). Every word earns its place; no fluff or 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?
For a simple one-parameter headlines tool, the description covers the core behavior, but without an output schema, the agent is left uncertain about the exact shape of each headline item (just text? includes link?). The description mentions 'stories' but doesn't clarify the output fields, so it's not fully complete for an agent to confidently invoke and parse the result.
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 has 100% coverage for the single parameter, including an enum and a description ('Moneycontrol section slug'), so the baseline is 3. The tool description adds no further parameter-level information beyond what the schema already provides, which is acceptable but not enhancing.
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 action ('Get'), the specific resource ('Moneycontrol section headlines'), and adds useful detail about the response (25 to 50 stories, without publication times). It is unambiguous and distinct from the many other headline tools by naming Moneycontrol explicitly.
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?
There is no guidance on when to use this tool versus the many other headline tools (e.g., nyt_headlines, cnn_headlines). The context is implied only by the tool name and source, but the description does not state any condition, alternative, or exclusion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.