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

No annotations are provided, so the description carries the responsibility for behavioral disclosure. The word 'Read' conveys a read-only intent, which is the most important behavioral trait. However, it does not explicitly state that no changes are made, what happens if templates are not configured, or whether any authentication or search prerequisites apply.

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 a single sentence with no filler and front-loads the core action 'Read'. It efficiently specifies both the email templates and the LinkedIn invite template without unnecessary detail. Every part of the sentence contributes meaningful 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?

The tool is simple, but with no annotations and no output schema, the description is the only source of operational context. It fails to explain the required search_id parameter, how the templates are scoped, or what the response contains. An agent cannot reliably know exactly what value to pass or what to expect back.

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%, so the description must compensate for the undocumented search_id parameter. It never mentions search_id or explains how it relates to the outreach content being read. The parameter name provides only a weak clue that it identifies a search, leaving the agent to infer the required value.

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 states a specific verb and resource: 'Read the configured email subject/body templates and LinkedIn invite template for SDR outreach.' It clearly identifies what the tool does and differentiates it from broader siblings like sdr_get_outreach by specifying exactly which content is retrieved. The title's '(templates)' further reinforces the resource scope.

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 no guidance on when to choose this tool over related siblings such as sdr_get_outreach, sdr_preview_outreach_content, or sdr_update_outreach_content. It does not mention exclusions, prerequisites, or alternative tools. The only usage signal is the verb 'Read', which implies retrieval but does not help an agent decide among the many SDR content-related tools.

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