create_class

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

No annotations are provided, and the description only states the basic action. It does not disclose behavioral traits like permission requirements, validation rules, side effects (e.g., immediate system impact), rate limits, or error conditions. The tool description carries the full burden for transparency but fails to deliver.

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 that conveys the essential purpose. It is concise and front-loaded, with no unnecessary words. However, it is almost too brief, leaving out important details that could be added without verbosity.

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 and a high number of sibling tools, the description is incomplete. It does not mention what the tool returns (e.g., the created class object ID or details), which is critical for an agent to process the result. The lack of usage context and behavioral details further reduces completeness.

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?

The input schema covers 50% of the parameters with descriptions, but the tool description adds no additional meaning beyond what the schema provides. It does not explain the parent_ref parameter's role in creating sub-classes or the optional company parameter's effect. For a tool with moderate schema coverage, the description should compensate but does not.

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 creates a new class in QuickBooks Online for categorizing transactions. The verb 'Create', resource 'class', and context 'QuickBooks Online for categorizing transactions' are explicit and distinguish it from many sibling create tools like create_account or create_department.

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?

The description provides no guidance on when to use this tool versus alternatives such as create_account, create_department, or other classification tools. There is no mention of scenarios where create_class is preferred nor any exclusion criteria.

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