get_top_bulk_buys

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

No annotations exist, so description carries full burden. It discloses ranking criterion and time scope ('today's'), and adds context about purpose. However, it does not mention mutability, rate limits, or data freshness, and could be more explicit about being read-only.

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?

Two sentences, front-loaded with core functionality in first sentence, second adds valuable context. 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?

Given no output schema or annotations, description adequately explains what the tool returns (top buys, ranked by value, today-only) and its utility. Could be slightly more complete by explicitly noting NSE context and that it is only for purchases, but overall strong.

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?

Parameter descriptions in the schema already cover 'limit' and 'symbol' with default and NSE scope. The tool description adds no extra parameter information. Since schema coverage is 100%, baseline score of 3 applies.

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?

Description clearly states it returns 'today's largest bulk-deal purchases ranked by total trade value (quantity × price)', which is specific and distinguishes from sibling tools like get_top_bulk_sells by specifying 'purchases' and 'institutional accumulation'.

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?

Description provides a use case ('spotting institutional accumulation') but lacks explicit guidance on when not to use or how it compares to siblings like get_bulk_deals or get_top_bulk_sells. The usage is implied but not fully directive.

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