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

The annotations already declare readOnlyHint=false (write), idempotentHint=true, and destructiveHint=false, covering key behavioral traits. The description adds context that the tool only accepts bounded structured specs and rejects binary bytes, which is useful for an agent deciding whether to call it. It does not, however, describe side effects, validation behavior, or error conditions, but with annotations carrying safety/idempotency, this is a moderate contribution.

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 a single sentence with no unnecessary words, and the core purpose is front-loaded. It earns its place as a concise overview, though it sacrifices detail in other dimensions. It is appropriately sized for a short description, though not over-verbose.

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 has 7 parameters, a nested object, and no output schema, yet the description offers only a one-sentence purpose statement. Without parameter documentation or additional context, an agent cannot reliably construct a valid request, especially for fields like details or the role of presentationId/requestId/sessionId/executionId. The annotations help with safety and idempotency, but the overall description is far too sparse for a tool of this complexity.

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 schema description coverage at 0%, the description carries the entire burden of explaining the seven parameters, but it names none of them. An agent cannot determine what projectId, idempotencyKey, details, or the optional ids mean from either the description or the schema property definitions (which lack descriptions). This is a critical gap, as even the purpose of required parameters like idempotencyKey is left unexplained.

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 states a specific action ('Store') and a specific resource ('bounded structured presentation specification'), which clearly identifies the tool's purpose. It also explicitly excludes binary asset bytes, which helps distinguish it from sibling presentation tools that might accept binary data. However, it does not name any sibling tools, so an agent must infer differentiation from this single boundary.

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 implies usage by defining the tool's input scope ('bounded structured presentation specification') and its exclusion ('without accepting binary asset bytes'), but it does not explicitly state when to choose this tool over alternatives like presentation_write or create_presentation_request. No prerequisites, exclusions, or alternative tool names are given. The statement gives a general boundary but not enough concrete guidance.

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