resend_raw

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

Annotations provide readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: true. The description adds that mutating methods are blocked in readonly mode, which is important behavioral context beyond annotations. It also labels the tool as an 'Advanced escape hatch,' implying it is low-level and powerful. No contradictions. Could mention rate limits or authentication aspects, but still good.

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 extremely concise: two sentences, front-loaded with the main purpose. Every sentence provides essential information. No wasted words.

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?

With no output schema, the description could explain return values, but since the tool is an escape hatch for arbitrary endpoints, the return format is endpoint-specific and cannot be generalized. The openWorldHint suggests the tool is flexible. The description is complete enough for its purpose, but missing a note about response format could be a minor gap.

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 100%, so baseline is 3. The description does not add extra parameter semantics beyond what the schema already provides. The schema itself has good descriptions for method and path. No additional insight from the description beyond the existing schema.

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 clearly states the tool's purpose: 'make a raw authenticated request to ANY Resend API endpoint not covered by a dedicated tool.' It uses specific verbs ('make a raw authenticated request') and a specific resource ('ANY Resend API endpoint'). It also distinguishes from sibling tools by advising to prefer specific tools when one exists.

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 provides explicit guidance: 'Prefer specific tools when one exists' and 'Mutating methods (POST/PATCH/PUT/DELETE) are blocked in readonly mode.' This tells when to use this tool (as a fallback) and when not (if a dedicated tool exists, or in readonly mode).

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