Add a database row

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

Discloses the write nature (consistent with readOnlyHint=false) and provides detailed value shape rules for various types. Lacks error handling or auth details, but annotations already cover safety profile.

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?

Four sentences, front-loaded with purpose, every sentence adds unique value. No redundant or vague language.

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 parameter semantics and usage guidance well. Missing return value description (output schema absent) and error scenarios, but overall comprehensive for a create tool.

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?

Adds significant value beyond schema by explaining value shapes per type (e.g., date format, select option name). The schema has 100% coverage but description deepens understanding.

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 the action ('Append a row') and the resource ('Rootr DATABASE'). It provides specific details about how to map values, distinguishing it from sibling tools like rootr_update_row.

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 advises calling rootr_read_database first to learn columns, providing clear prerequisite guidance. Doesn't explicitly state when not to use, but the context of adding a row is clear.

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