b24_list_methods

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

The description explains that it calls 'scope' and optionally 'methods' based on the 'full' parameter, and describes the return format. This adds behavioral context beyond the annotations (readOnlyHint, idempotentHint), which already signal safe, non-destructive behavior.

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 plus a return format line, no wasted words. The key purpose is front-loaded, and every sentence contributes meaningful information.

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 low complexity (0 required params, full schema coverage, existing output schema description, and annotations covering safety), the description adequately informs the agent of the tool's purpose, behavior, and return format.

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 input schema has 100% description coverage for all 3 parameters, fully explaining each. The description only mentions 'full=true' to list methods, adding minimal extra value beyond the schema. Baseline 3 is appropriate.

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 'Discover which REST methods/scopes this webhook can access.' It uses a specific verb (discover) and resource (methods/scopes), and is distinct from sibling tools like b24_bizproc_template_list or b24_call.

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?

Indicates usage context: 'Handy for figuring out what the portal exposes before writing a b24_call.' It provides a clear when-to-use hint, though does not explicitly state when not to use or list alternatives.

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