betadrop_help

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It conveys that this is a read-only reference operation with no side effects and hints at the response content (tools, inputs, example prompts). It does not disclose whether authentication is required or the exact output format, but the non-mutating nature is reasonably clear.

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?

A single front-loaded sentence of 17 words with zero waste. 'Get a quick reference' opens with the action, and every phrase ('all available', 'their inputs', 'example prompts') adds distinct value.

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 0-parameter help tool with no output schema, the description is nearly complete: it states the purpose and what the agent will receive. The only minor gap is the lack of explicit guidance on whether login is a prerequisite, which could matter given the authentication-focused siblings.

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 the baseline is 4 per the rubric. The description correctly implies no inputs are needed, and there is nothing about parameters that needs further explanation.

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 a quick reference') with a clear resource (all BetaDrop MCP tools) and specifies what it returns (inputs and example prompts). It distinguishes itself from all functional siblings like betadrop_publish or betadrop_token_create by being the meta-level orientation tool.

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 usage context is implied: an agent would call this when it needs an overview of available tools, inputs, or example prompts. However, there is no explicit statement of when to use it versus alternatives, no exclusions, and no mention of whether it works without authentication despite the existence of betadrop_login.

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