tdarr_cruddb

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

With no annotations, the description must disclose behavioral traits like side effects (e.g., destructive delete mode), auth needs, or rate limits. It only lists parameter requirements, omitting any warnings or behavioral context.

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 efficiently listing modes and required parameters. It is front-loaded with the purpose, but the dense formatting (e.g., 'Modes: insert (requires collection, docID, obj)') could be slightly clearer.

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?

Given the complexity (5 params, 6 modes) and lack of output schema, the description should explain return values, error behavior, or pagination. It provides none of this, leaving the agent with minimal context for a database CRUD 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?

Schema coverage is 100%, so baseline is 3. The description adds value by explicitly tying parameters to modes (e.g., 'insert requires obj'), clarifying conditional requirements beyond the schema's per-property descriptions.

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 tool interacts with a database and lists six specific modes (insert, getById, etc.), making the purpose and scope unambiguous. It distinguishes itself from siblings like tdarr_search_db by providing more general CRUD operations.

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 is provided on when to use this tool versus alternatives (e.g., tdarr_search_db). There is no mention of prerequisites, when not to use, or which mode to prefer in different scenarios.

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