get_help

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions support for 'specific categories or keyword search', which is a behavioral trait, but lacks details about how the tool actually behaves (e.g., whether it returns a list, requires follow-up, or has restrictions). This is minimal but not absent.

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 short, front-loaded sentences. Every word is informative and no filler exists. The structure is clean and easily parsed.

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 zero-parameter, no-output-schema tool, the description conveys the core purpose but omits practical details like how the 'keyword search' is initiated given no parameters. It is adequate but leaves questions about the interaction model, so it is not fully complete.

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 tool has zero parameters, so there is no schema detail to augment. The description's mention of categories and keyword search adds context that could guide invocation, though it is somewhat underspecified. Baseline for 0 parameters is 4, and the description does not detract.

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 tool provides 'help and troubleshooting guidance for InfluxDB operations', using a specific verb and resource. It is distinct from sibling tools, which are all operational (queries, tokens, databases), so the purpose is unambiguous.

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 implies usage as a help resource but does not explicitly state when to prefer it over other tools or any exclusions. The phrase 'Supports specific categories or keyword search' hints at interaction modes but stops short of clear guidance on when to invoke this tool.

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