b2_get_bucket_notification_rules

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds valuable behavioral context beyond them: required permissions (readBucketNotifications or writeBucketNotifications), explicit 'no side effects', and redaction of sensitive webhook fields in the MCP response. This is meaningful transparency not available from structured fields alone.

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?

Three sentences, front-loaded with the core purpose, and every sentence adds value: usage context, authorization, side effects, and response redaction. There is no redundant or filler wording.

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 low complexity (one parameter, no output schema), the description covers everything an agent needs: what it does, when to use it, required permissions, safety profile, and sensitive data redaction behavior. Nothing essential is missing.

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?

Schema description coverage is 100% and the single bucketId parameter is already well documented ('Exact bucket ID whose notification rules should be read'). The description does not need to add parameter detail, so the 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 states a specific verb ('Read'), a specific resource ('B2 event-notification webhook rules for a bucket'), and explicitly distinguishes this tool from its sibling b2_set_bucket_notification_rules. An agent can immediately understand what the tool does and which sibling it complements.

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 says to use this tool before b2_set_bucket_notification_rules to diff or preserve existing rules, because the set operation replaces the complete rule set. This gives clear when-to-use guidance and names the natural alternative, earning full credit.

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