get_top_bulk_sells

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

No annotations are provided, so the description must fully cover behavioral traits. It only states the tool returns top bulk-deal sales, but does not disclose that it is read-only, the time horizon ('today's' is ambiguous), or any limitations like rate limits or authentication needs. The description is too sparse for a tool with no 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?

The description is two sentences with no extraneous information. It is front-loaded with the main purpose and adds a use case in the second sentence. Every word serves a purpose.

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 presence of sibling tools (e.g., get_bulk_deals, get_top_bulk_buys) and lack of output schema, the description is minimal. It does not explain the returned fields, data source, or whether 'today's' refers to the current trading day. The description is adequate for a simple list but lacks details needed for informed selection.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema for the parameters (limit and symbol). It does not explain how they affect the ranking or filtering beyond what the schema already says.

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 the tool returns 'Today's largest bulk-deal sales ranked by total trade value.' It specifies the resource (bulk-deal sales), action (get top), and sorting (by total trade value), distinguishing it from related sibling tools like get_top_bulk_buys.

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 includes 'Useful for spotting institutional distribution,' which gives a use case. However, it does not explicitly state when not to use this tool or compare it to alternatives like get_bulk_deals or get_top_bulk_buys. The guidance is implied but not fully explicit.

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