Low-level transform (full passthrough)

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

No annotations are present, so the description must fully describe behavioral traits. It only says 'low-level transform (full passthrough)' and 'escape hatch', but does not disclose side effects, authentication needs, rate limits, return value, or whether the payload is validated or executed immediately. This is insufficient for an agent to understand the consequences of invoking the tool.

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 at two sentences, with the most critical information (purpose and usage guidance) placed first. However, it sacrifices necessary detail for brevity, earning a 4 rather than 5.

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?

Given the tool's complexity (4 parameters, nested objects, no output schema, no annotations), the description is severely incomplete. It lacks information on parameter construction, default behavior, error handling, and the nature of the 'full passthrough'. Sibling tool descriptions may help, but the description itself falls short.

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?

With 0% schema description coverage and no annotation, the description adds no meaning to the parameters. It mentions three top-level properties (rightsContexts, processingContexts, requests) but omits loggingContext and provides no explanation of their structure or usage. The agent cannot determine how to construct valid parameter values.

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 is an 'escape hatch' for sending a fully-formed Engine transform payload, explicitly distinguishing it from higher-level tools protect/unprotect/search. The verb 'send' and resource 'Engine transform payload' define its purpose precisely.

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: use for advanced cases like multiple contexts or dependency contexts, and recommends preferring protect/unprotect/search for simpler use. This clearly tells when and when not to use the tool.

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