Data: create

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

Annotations already cover the safety profile (readOnly=false, destructive=false). The description adds genuine behavior beyond them: it returns the created record with its new id, auto-stringifies objects/arrays for jsonb fields, and discloses that EntityCreated workflows will fire — a meaningful side effect an agent should know.

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?

Front-loaded with the core action, then consequences and the sibling route. No filler sentences — each one (id return, jsonb coercion, workflow trigger, bulk alternative) earns its place.

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 2-parameter create tool with no output schema, the description covers the payload format, return shape, side effects, and the bulk-load escalation path. Nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3. The description goes beyond the schema by explaining the data payload is a JSON map of field names to values and that jsonb objects/arrays are auto-coerced to JSON strings, adding real semantic value for the 'data' parameter.

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?

States a specific verb (create) and resource (record), and clarifies it inserts exactly one record from a JSON object and returns it with a new id. It distinguishes itself from siblings like data_import, data_update, and data_delete without the agent needing to open any schema.

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?

Explicitly routes bulk loading to the alternative: 'To load many rows from a file, use `data_import`.' This gives a clear condition for choosing a sibling, though it doesn't spell out other when-not cases (e.g. via API vs file).

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