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. The description adds useful domain behavior beyond annotations: Cloud Patrol scans Threads every 15 minutes and replies to fresh posts through the official API, and it lists the status fields returned. It still lacks details such as auth requirements or rate limits, but the added context is meaningful.

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 three tight sentences and front-loads the return fields. The cadence sentence directly supports interpreting 'last scan time,' and the final sentence gives usage context. No sentence is wasted.

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 simple read-only tool with one fully documented parameter, rich annotations, and no output schema. The description enumerates the returned configuration/status fields, explains Cloud Patrol behavior, and states when to call it, which is sufficient for an agent to invoke it correctly.

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?

There is only one parameter, account_id, and schema description coverage is 100%, with the schema itself describing it as 'Account id.' The description references 'an account's' configuration but adds no format, constraints, or selection guidance for account_id. Baseline 3 is appropriate because the schema already carries the parameter documentation.

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 gives a specific verb and resource: 'Returns an account's cloud patrol configuration and status,' then enumerates fields like keywords, daily cap, replies sent today, review_before_reply, and last scan time. It clearly separates this from a settings mutation, but it does not explicitly contrast with nearby siblings such as cloud_patrol_log or cloud_patrol_stats.

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?

It explicitly states when to use the tool: 'Applies before changing patrol settings or when the user asks whether patrol is on.' That is clear usage context. It does not name alternative tools like set_cloud_patrol, cloud_patrol_log, or cloud_patrol_stats, nor does it provide when-not-to-use guidance.

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