monobank-get-webhook

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the behavioral detail that an empty string means no webhook is set, which is valuable beyond the annotations and helps the agent interpret the return value.

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?

The description is two short, direct sentences. It front-loads the verb and resource, then adds the crucial empty-string clarification. Every word earns its place with no 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?

This is a parameterless read tool with no output schema. The description fully explains what the agent receives (the webhook URL) and handles the special empty-string case. Given the sibling context and simplicity, there are no missing behavioral details.

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 zero parameters, so there are no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description doesn't need to add parameter details since none exist.

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 states exactly what the tool does: it returns the currently configured webhook URL for the Monobank token. The verb 'Returns' is specific, the resource ('webhook URL') is clear, and the scope ('for this Monobank token') distinguishes it from sibling tools like set/unset webhook.

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 provides clear context that this is a read operation for the current webhook configuration and adds the important empty-string semantics. It doesn't explicitly say 'use this before setting/unsetting a webhook', but the intent is obvious given the sibling tools are mutations, so a 4 fits.

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