apex_add_file_upload

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

The description goes beyond the annotations by revealing the compound behavior: it adds both a FILE_BROWSE item and an after-submit process. It also explains the purpose of the process (storing uploads as BLOB), which adds context not present in the readOnlyHint=false or destructiveHint=false annotations.

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 front-loads the action and purpose. Every word contributes value, with no filler or redundant phrasing.

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 the tool's complexity (10 parameters, compound action), the description is adequately complete. It mentions the essential components (item + process) and the storage goal. The presence of an output schema and comprehensive parameter descriptions reduces the need for the description to explain return values or parameter formats.

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 all parameters with detailed descriptions (100% coverage), so the description does not need to add parameter semantics. The description itself mentions no parameter details, but the schema handles this dimension adequately, earning the baseline score.

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 specific action: 'Add a FILE_BROWSE item + after-submit process to store uploads as BLOB.' It uses a specific verb (Add) and a specific resource type (FILE_BROWSE item), distinguishing it from other add_* siblings like apex_add_item or apex_add_process.

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 clearly implies when to use this tool: whenever file uploads need to be stored as BLOBs. It does not explicitly name alternatives or exclusions, but the context is unambiguous, and the combination of FILE_BROWSE + after-submit process makes its purpose distinct among siblings.

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