help

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

No annotations are provided, so the description carries full responsibility. It correctly communicates the tool's read-only, non-destructive nature (guidance only) but does not detail the format or scope of returned guidance. For a simple help tool, this is adequate but not rich; additional specifics on output would improve transparency.

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 with no wasted words. The first sentence states what the tool does, and the second gives usage guidance. Perfectly front-loaded and concise.

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 tool's simplicity (no parameters, no output schema), the description is nearly complete: it explains the purpose and usage context. Minor improvement could specify that guidance is returned as text or lists, but overall it sufficiently enables agent selection and invocation.

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?

With 0 parameters and 100% schema coverage, the baseline is 4. The description adds value by explaining that the tool returns guidance on tools and entities, giving meaning beyond the empty schema. No further parameter details are needed.

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 'concise developer guidance' on 'available Billforward MCP tools and entities', with a specific verb ('get guidance') and resource ('tools and entities'). This distinguishes it from sibling tools that perform specific actions (e.g., create, cancel, list), making its purpose 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 explicitly states when to use the tool: 'if you are unsure which tool to use.' This provides clear context. While it does not mention when not to use it, the nature of a help tool makes alternatives unnecessary; the guidance is appropriate for a fallback.

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