Webhook receiver status

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

Discloses that it does NOT call the Avito API, which is critical behavior not in annotations. Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and description adds context about local check.

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, no wasted words. First sentence states the return value, second provides usage context. Efficient and info-dense.

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?

Without output schema, description explains all returned fields (enabled, URL, subscribe URL, ring-buffer counters). Also includes behavioral note about not calling API. Complete for a no-param tool.

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?

No parameters, baseline 4. Schema coverage is 100%, description adds no param details but none 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?

Description clearly states it returns configuration and live stats of the Avito webhook receiver, listing specific fields. It distinguishes itself from messenger_register_webhook and messenger_get_webhook_events by name and purpose.

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?

Explicitly tells when to use this tool: 'Use it to verify the receiver is set up before messenger_register_webhook, then read collected events with messenger_get_webhook_events.' Provides a clear usage order.

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