qbo_attachables_create

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

The description only says 'Create' indicating a write operation but lacks any behavioral details such as side effects, permissions required, idempotency, or what happens when required fields are missing (none required). No annotations are provided to compensate.

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 concise sentence that efficiently conveys the core purpose. However, it is too brief to cover additional necessary information, preventing a higher score.

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 no output schema, 6 optional parameters, and no annotations, the description does not adequately explain behavior when parameters are omitted or conflicting (e.g., both Note and FileAccessUri). The completeness is insufficient for an AI agent to reliably decide and configure the 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?

All 6 parameters have descriptions in the input schema (100% coverage), so the schema already provides meaning. The description adds no additional parameter details, hence a baseline score of 3.

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 states 'Create a new Attachable record in QuickBooks Online' which clearly indicates the action (create) and resource (Attachable record). It distinguishes from siblings like qbo_attachables_get/list/update/upload, though it doesn't explain what an Attachable is.

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 versus alternatives like qbo_attachables_upload. No context on prerequisites, when to choose this over other create tools, or what scenarios are appropriate.

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