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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the change affects only new sends, which is valuable timing information, but it does not mention whether existing templates are overwritten, whether the operation is reversible, or what state the outreach must be in.

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 short sentences, front-loaded with the verb and object, with no filler. The second sentence about new sends adds essential timing information and earns its place.

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 simple one-parameter mutation tool, the description is adequate but leaves gaps: no explicit parameter semantics, no guidance among SDR sibling tools, and no side-effect detail beyond the new-send timing. Without annotations, a bit more detail would make the tool self-sufficient for an agent.

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 the description never explains search_id, its format, or how it targets the outreach. The parameter name and the phrase 'this SDR outreach' hint at the intended mapping, but the agent must infer the meaning rather than being told.

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 uses a specific verb ('Edit'), a clear resource ('email/LinkedIn templates for this SDR outreach'), and adds a meaningful scope detail. This effectively separates it from read-only and preview siblings such as sdr_get_outreach_content and sdr_preview_outreach_content.

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 gives clear context that edits apply to templates and take effect on new sends, but it does not explicitly say when to use this versus sibling tools like sdr_get_outreach_content or sdr_preview_outreach_content. Usage is implied rather than stated with alternatives or exclusions.

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