contentrain_content_save

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

Annotations already provide readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral traits: auto-commit to git and media field normalization behavior, which go beyond annotations without contradiction.

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 relatively long but well-structured with clear sections for each model kind. It is front-loaded with the main purpose and every sentence adds value, though could be slightly more concise.

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 save operation with no output schema, the description covers input variations comprehensively and includes important context like git auto-commit and media field handling. It does not describe errors or return values, which is acceptable given the tool type.

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 coverage is 100% with descriptions for all properties. The description adds significant meaning by explaining how 'id', 'slug', and 'data' are treated per model kind, and specifics about media fields, enhancing understanding 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 'Save content entries' and provides detailed explanations for each model kind (DICTIONARY, COLLECTION, DOCUMENT, SINGLETON), which is specific and distinguishes this tool from siblings like contentrain_content_delete and contentrain_content_list.

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 implicitly indicates when to use this tool (to save content entries) and includes a warning against manually editing .contentrain/ files after calling, but does not explicitly mention alternatives or when not to use it. Given no sibling save tools, this is adequate.

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