Record Context Consumption

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

Discloses important behavior beyond annotations: it's a canonical mutation with no client idempotency key, advising not to retry automatically. Also clarifies human approval is not required and describes failure modes. This adds significant context not available from annotations alone.

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?

Well-structured with clear sections, but somewhat verbose due to detailed failure enumeration. Could be more concise without losing essential guidance.

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 presence of an output schema and annotations, the description provides comprehensive guidance on usage, failure handling, and behavioral expectations. It covers when to use, when not, and what to do on various failures.

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 only 20% (only projectId has a description). The tool description does not elaborate on the meaning of executionId, contextPackageId, impressionIds, or actualPromptHash, leaving the agent with minimal understanding of parameter purposes beyond the sparse 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 explicitly states 'Record that a delivered ContextPackage was actually used by an AIExecution'—a specific verb+resource. It distinguishes from sibling tool 'confirm_context_delivery' by noting that delivery and consumption are separate facts.

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 explicit 'Use when:' and 'Do not use when:' conditions, including when to avoid using (narrower tool, unresolved scope, user declined). Also includes failure handling instructions, guiding correct invocation.

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