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

No annotations are provided, so the description carries the full burden. 'Read' weakly implies read-only behavior, but there is nothing about permissions, what happens on an invalid/missing search_id, or default values when templates are unconfigured.

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?

One economical sentence with the resource front-loaded and no filler. It is appropriately short for a simple read tool, though it could have spent a few more words on the required identifier.

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?

The description names the returned content well, but with no output schema and an undocumented required parameter, an agent cannot fully know how to invoke it correctly. Adequate but with an obvious gap around search_id.

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 coverage is 0% for the single required parameter, search_id, and the description never mentions it. The agent gets no guidance on what the identifier refers to or how it scopes the returned templates, so the description does not compensate for the coverage gap.

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 verb 'Read' plus the resource ('email subject/body templates and LinkedIn invite template') is specific and concrete about what content is returned. It distinguishes itself from the plain sdr_get_outreach and the rendered sdr_preview_outreach_content by naming templates, though it does not explicitly call out those siblings.

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 statement of when to use this vs. sdr_get_outreach, sdr_preview_outreach_content, or sdr_update_outreach_content. The read-the-templates intent is only implied by the verb, so the agent must infer the routing decision.

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