contentrain_bulk

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

Adds auto-commit context beyond annotations. However, does not disclose that delete_entries requires confirm=true or that operations are irreversible.

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?

Two concise sentences, no filler. Front-loaded with key information.

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?

Covers core idea but lacks details about operation-specific requirements, error handling, and effect on git history. No output schema to supplement.

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 high (86%), so description adds minimal value. Description reiterates 'operations' but does not clarify dependencies like required fields for each operation.

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?

Description clearly states 'batch operations on content entries' with auto-commit to git. It implies bulk nature but does not explicitly distinguish from sibling single-entry tools like contentrain_content_delete.

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?

No guidance on when to use this tool vs individual operations (e.g., contentrain_content_delete for single delete). Does not explain operation selection criteria.

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