user_connection_add

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

No annotations provided. Description indicates mutation ('Add/update') and per-user scope, but does not disclose side effects, authentication needs, rate limits, or behavior on update (overwrite/merge). Insufficient for a tool with no annotation coverage.

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 sentences, no fluff. Concise and front-loaded with key purpose.

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?

12 parameters, no output schema, moderate schema coverage. Description does not explain return values, update vs add behavior, or connection type selection logic. Incomplete for a complex tool with many optional fields.

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 description coverage is 58%. Description only hints at parameter groups ('Supports Odoo, SSH, and Portainer settings') without explaining each parameter's role or how connection types are determined. Does not compensate for schema gaps.

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 'Add/update a personal Odoo connection (saved per-user)', specifying verb, resource, and scope. It distinguishes from sibling tools like user_connection_list and user_connection_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?

Implies usage for managing personal connections, but lacks explicit guidance on when to use Odoo vs SSH vs Portainer settings. No mention of prerequisites or when not to use.

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