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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is structured data. The description adds real behavioral context beyond that: it clarifies the semantic boundary that a read-capability summary is not an authorization to send or write, which is precisely the ambiguity an agent could misread.

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, zero filler, with the capability scope front-loaded and the boundary caveat second. Every clause carries information an agent needs.

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?

Output schema exists, so return values need not be described, and annotations cover the safety profile; a zero-parameter read tool therefore needs little more. The description covers scope, content and the send/write boundary, though it says nothing about ordering or pairing with explain_policy beyond the negative case.

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 tool takes zero parameters, so per the rubric the baseline is 4 and the description has nothing parameter-specific to add. It correctly avoids inventing inputs and instead spends its words on scope and boundaries.

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?

States a specific verb (explain) and a precise subject (what this AI connection can read right now), then enumerates the included content: source settings, account limits, quiet mode, voice setting. It also routes the agent away from a sibling by naming explain_policy, so get_settings_summary can be told apart from explain_policy/explain_access without opening either schema.

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?

Gives an explicit when-not and a named alternative: it does not confer send/write permission, and explain_policy is the tool for that. It does not positively state the trigger condition (e.g., 'call this first to see what reads are available'), so it falls short of a full when/when-not/alternatives triple.

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