vbcs_export_bo_data

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

There are no annotations to fall back on, and the description only repeats the action of exporting without disclosing behavioral traits. It does not explain what the export output looks like, whether it is a downloadable file or an array of data, or any side effects or permissions needed. For a tool with no annotation coverage, this is insufficient.

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 one concise, front-loaded sentence with no redundancy or filler. It effectively communicates the core action. However, it is so brief that it sacrifices valuable details, making it not quite a 5.

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?

With 3 required parameters and no output schema, the description is inadequate for an agent to invoke the tool correctly. It does not mention return values, prerequisites, or any operational constraints. The information provided is minimal and leaves many gaps that would require additional investigation or assumptions.

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 schema has 0% description coverage, and the description does not explain any of the three required parameters (boName, appName, appVersion). The parameter names are somewhat self-explanatory, but the description adds no additional meaning or context, leaving the agent to guess how to fill them correctly.

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's function with a specific verb 'Export' and a specific resource 'a business object's data records', and it also specifies the context 'from a standalone VBCS instance'. This distinguishes it from sibling tools like list_apps or vbcs_list_applications, which are about listing, not exporting data.

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. It does not mention any exclusions, prerequisites, or comparisons to sibling tools such as read_artifact or vbcs_list_applications. The only contextual hint is 'standalone VBCS instance', but this is not developed into actionable usage guidance.

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