create_custom_item

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It indicates a write operation but does not mention the required confirm flag, permission needs, side effects, or any additional execution requirements. This is a meaningful gap for a mutation 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 a single sentence with no filler or redundancy. It front-loads the primary action and object. However, it is concise to the point of omitting important behavioral context, so it earns a 4 rather than a 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?

The tool has a complex nested template schema, five parameters, and no output schema or annotations. A one-sentence description is not enough to guide correct invocation. It does not explain the confirm requirement, the distinction between vaultName and shareId, or the agentReason field, leaving too much for the agent to infer.

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 the schema already documents all parameters in detail. The description adds only the idea of 'template payload' and 'vault or share,' which loosely maps to template, vaultName, and shareId. It does not add meaningful semantics beyond the 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 a specific verb and resource: 'Create a custom item from template payload in a vault or share.' It identifies the action and the main target. It distinguishes from specialized create tools somewhat by emphasizing 'custom item' and 'template payload,' though it does not explicitly differentiate from create_login_item_from_template.

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?

Usage is implied: use this when creating a custom item from a template payload. However, there is no explicit when-to-use or when-not-to-use guidance versus sibling tools such as create_login_item_from_template or create_note_item. No alternatives or exclusions are mentioned.

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