help_bulk_api

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

The annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds that the tool provides guidance on workflows and patterns, but does not go into deeper behavioral details such as response format or how topics are presented; however, the output schema and topic enum reduce the need for that.

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 concise sentences with no filler. The main purpose is front-loaded, and the second sentence adds actionable usage guidance 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?

For a help/documentation tool, the description plus the rich input schema and output schema give the agent everything needed to call it correctly: required topic, available enum values, optional tool parameter, and read-only annotations. No critical context is missing.

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 the topic and optional tool parameters are already well documented. The description adds general context about the 3-step workflow and patterns, which maps conceptually to some enum values, but it does not add detailed semantics beyond the schema.

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 uses a specific verb ('Get help and guidance') with a clear resource ('Bulk API for loading timeseries data') and elaborates on the key workflow ('3-step workflow and common patterns'). This makes it readily distinguishable from the sibling query and data tools, which target different operations.

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?

It explicitly says 'Use this to understand the 3-step workflow and common patterns,' giving clear context for when the tool is appropriate. It does not name alternative tools or exclusions, but the guidance is sufficient for an agent to recognize this is the help entry point for Bulk API usage.

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