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

Annotations indicate a non-read-only write operation (readOnlyHint=false), and the description adds no further behavioral detail about side effects or permissions. However, the entity parameter description includes a useful compliance caveat—do not send government identifiers, birth dates, or card-processing details—which goes beyond the annotations by warning about data handling.

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 front-loaded sentence with no wasted words, stating the verb, resource, and target system immediately. It is appropriately terse, though it omits usage guidance that would make it fully self-sufficient.

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?

The definition is minimally viable: it names the operation clearly and the schema covers parameters, but the entity is a freeform object with no documented required fields. With no output schema, the expected result is undisclosed, and the agent must rely on external QuickBooks API knowledge to construct a valid Department object. The compliance warning helps, but overall the context is incomplete.

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 100%, so the baseline is 3. The entity description identifies the expected QuickBooks API v3 Department object and adds a compliance warning, while the company parameter is clearly described with an optional-when-single-company note. The tool description itself adds no parameter meaning beyond what the schema provides.

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 a specific verb ('Create'), resource ('department'), and target system ('QuickBooks Online'), making it clear what the tool does. It is easily distinguished from update_department, get_department, and search_departments, though it does not explicitly contrast with sibling create_* tools.

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 like update_department or create_class. There is no mention of prerequisites, such as checking whether the department already exists, or any exclusions that would route an agent to another tool.

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