Classify a document

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

The only annotation is openWorldHint, so the description carries most of the behavioral burden. It usefully discloses credit cost and synchronous waiting, but omits timeout behavior, permission needs, and what 'the answer' contains.

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 tight sentences with the core action front-loaded and cost information clearly appended. There is no redundant or wasted wording.

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?

For a five-parameter classification tool with no output schema, the description is too thin about what is returned and how failures or timeouts behave. It also omits the upload prerequisite workflow and alternatives that an agent would need for correct routing.

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 description clarifies that document_id refers to one uploaded document and that classes come from the account, adding some meaning beyond the schema. It says nothing about multi_class, include_unknown, or instructions, leaving clear gaps alongside the 60% schema coverage.

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 and resource: classify one uploaded document into the account's classes. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as extract or standardize.

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?

It implies the document must already be uploaded and that the call waits synchronously for a result. However, it gives no explicit when-to-use guidance versus extract, standardize, or list_classes, and no exclusions or failure conditions.

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