Create Platform Cache Partition

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

Annotations already indicate a non-read-only, non-destructive, idempotent operation. The description adds useful context (Metadata API, session vs org cache, default partition) but does not disclose potential failure modes, deployment delays, or permission requirements beyond what annotations provide.

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 concise at three sentences, front-loaded with the primary action. It includes a brief background on Platform Cache value, but every sentence contributes meaning without unnecessary fluff.

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 creation tool with well-documented schema, the description covers the core purpose and key distinctions. However, it omits details like capacity constraints (org-level limits), behavior on duplicate names, and whether the Metadata API operation is synchronous or requires deployment status checking, which would make it more complete.

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%, with every parameter documented in the input schema. The description adds no new parameter details beyond reinforcing the distinction between session and org cache sizes and the default partition flag, which are already 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 ('Creates') and identifies the precise resource (Platform Cache partition) via Metadata API. It clearly differentiates from sibling creation tools by focusing on cache partitioning.

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 explains when this tool is useful (improving app performance via server-side caching) and describes the two cache types. It does not explicitly mention when not to use it or alternatives, but the context is sufficient for most cases.

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