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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by describing the return content (enabled state, ordered rules, rule IDs) and by warning that the sibling write overwrites the entire rule list, which is a real behavioral hazard an agent should know. It stops short of discussing what happens when a receptionist has no alerts configured or unmapped states.

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 short sentences, front-loaded with the purpose before the prerequisite and the sibling warning. No filler, and every clause carries actionable 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?

For a single-parameter read tool with no output schema, the description supplies what the annotations can't: the shape of the returned data, how to obtain the required ID, and the sequencing rule against the destructive sibling. Nothing an agent needs to invoke it correctly 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?

With a single parameter at 100% schema coverage, the baseline is 3, but the description earns more by naming the source of the value ('Get agentId from listAgents'), which the schema itself does not say. It still doesn't note edge cases such as invalid or cross-account agent IDs, so it isn't exhaustive.

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 and resource ('Read one receptionist's Lead Alerts') and enumerates what is returned: on/off state, ordered rules that call or text a team member after a matching inbound call, and rule IDs. It also implicitly distinguishes itself from lead_alerts_replace, so an agent can tell the read from the write 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?

Explicitly gives the prerequisite ('Get agentId from listAgents') and an ordering constraint with the reason ('Read this before changing alerts: lead_alerts_replace overwrites the whole rule list, so start from what this returns'). That names the alternative tool and the condition that sequences them.

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