sendcraft_get_email

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation via 'Retrieve', but does not disclose error behavior, auth requirements, or rate limits. Minimal but not misleading, hence a mid-range score.

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 core action and purpose, no filler. Every word adds value, making it highly concise and easily scannable.

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 with one parameter and no output schema. The description covers what it does, the use case, and the parameter source. However, 'details' is slightly vague and the return/error behavior isn't addressed, though this is borderline acceptable for a simple retrieval tool.

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 documents 'email_id' with a helpful source note ('returned from send or list calls'). The tool description adds context about checking a specific email but does not add new syntax or format details beyond the schema, which is already 100% covered.

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 'Retrieve' and clearly targets 'a single email by its ID', explicitly distinguishing from list operations. The phrase 'delivery status' adds precision and communicates exactly what the tool returns.

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?

Provides an explicit use case: 'check whether a specific email was delivered, opened, or bounced.' While it doesn't explicitly name alternative tools like sendcraft_list_emails, the context is clear for single-email status checks, which is sufficient for a simple retrieval tool.

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