pob_export_xml

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: it uses the native SaveDB serializer (output fidelity) and does not write a file, which is exactly the side-effect an agent might otherwise assume. Return transport (how the XML is delivered) remains unstated.

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?

A single compact sentence with the operation front-loaded, followed by the two facts that matter most (native serializer, no file write). Nothing is redundant or padded.

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 zero-parameter tool with no output schema, the description covers what it does and its main side-effect guarantee, which is close to sufficient. It does not state what exactly is exported (the whole current build?) or how the XML is returned, leaving a gap given there is no output schema to explain the response.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema is closed (additionalProperties=false) and empty, consistent with the description's parameterless framing.

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 names a specific verb (export) and resource (XML), and clarifies that it uses the original SaveDB serializer, which distinguishes it from the inverse sibling pob_import_xml. It does not explicitly name a sibling, so differentiation is inferred rather than stated.

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 only implied: the phrase 'без записи файла' (no file write) suggests this is the choice when the agent wants XML in-band rather than a file artifact. No explicit when-to-use/when-not, no prerequisites, and no named alternative such as pob_import_xml or a file-writing path.

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