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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the payload covers running state and limits, which is useful but thin; it says nothing about permissions, freshness, or what 'limits' contains.

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?

A single front-loaded sentence with no filler; the core outcome is stated immediately and nothing 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?

There is no output schema and no annotation coverage of parameters, so the description carries the burden for a two-required-param read tool. It does not explain the two identifiers or the shape of the returned policy, leaving the agent under-informed.

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 0% and both projectId and siteId are required strings with no constraints beyond minLength. The description provides no meaning for either parameter, so an agent must guess scope (which project, which site) entirely from the names.

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 (read) and resource (outreach automation policy) plus its content: whether the agent is running and its limits. That is clear enough to distinguish from mutation siblings like set_outreach_automation_status. It stops short of naming or contrasting with the closest read sibling, get_outreach_automation_overview.

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?

There is no when-to-use or when-not-to-use guidance. Nothing tells the agent how this differs from get_outreach_automation_overview, get_outreach_sending_dashboard, or get_outreach_automation_policy's mutation counterparts, so the choice among these reads is left to inference.

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