ExportClassToFile

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

With no annotations, the description carries the full burden. It does disclose real side effects: files are written to the tmp folder and the folder is auto-created if missing. However it omits overwrite behavior, required authorizations, and what happens to pre-existing files of the same name.

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?

Three short sentences, front-loaded with the primary action and destination, then the optional include behavior, then the folder-creation side effect. No filler, though the trailing sentence could have been merged.

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 three-parameter export tool with no output schema and no annotations, the description covers destination, optional include scope, and a key side effect. It would be complete at 5 with a note on returned file paths or overwrite semantics, but nothing critical blocks correct invocation.

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 class_name, single_file, and include_types are already documented in the schema. The description only restates the include-export idea ('optionally export all includes') without adding syntax, defaults, or behavior beyond the schema, so baseline 3 applies.

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?

States a specific verb (Export) and resource (ABAP class) with the destination (file(s) in the tmp folder), which clearly separates it from read-only siblings like GetClass or GetClassInclude. It does not explicitly name a sibling to disambiguate from ImportClassFromFile, so it stops short of a 5.

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?

Usage is implied by the verb and destination ('export directly to file(s)'), but there is no explicit when-to-use or when-not guidance, and no mention of the inverse ImportClassFromFile sibling or when to prefer GetClass for in-context reading.

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