Get Single Send Campaign

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Get detailed content and settings' without elaborating on return format, pagination, auth requirements, or whether the operation is read-only. The description adds minimal value beyond the tool's name/title, leaving the agent to infer behavior.

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, focused sentence with no unnecessary words. It front-loads the core action and resource, making it easy to scan and immediately actionable.

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 get-by-ID tool with one parameter and no output schema, the description is adequate but vague: 'detailed content and settings' does not specify what exact fields or nested objects are included. The presence of related tools (open_single_send_stats, list_single_sends) suggests more context could be useful, but the low complexity keeps this at a minimal viable level.

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?

The schema already fully describes the single parameter (singlesend_id) with a clear description. The tool description adds no additional semantic value for the parameter, so it meets the baseline for high schema coverage.

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 ('Get') and resource ('single send campaign') with scope ('detailed content and settings'). It clearly distinguishes from sibling tools like list_single_sends (which lists) and open_single_send_creator (which opens a UI), making the tool's purpose unambiguous.

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 implies usage for retrieving details of one specific campaign, but it does not explicitly state when to prefer this over list_single_sends or open_single_send_stats. No exclusions or alternative recommendations are provided, so the guidance is only implicit.

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