whodb_platform_bundle_export

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, but the description adds genuinely additive behavior: secret values are never exported, and file content is conditional on include_files and capped by max_file_bytes. It stops short of covering scale limits, auth/permission needs, or the bundle's output format.

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?

Four tight sentences, purpose front-loaded, and each subsequent sentence adds a distinct fact (contents, redaction, file gating, workspace scoping). No filler.

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 read-only export with a full schema and an output schema, the description covers what matters: scope, redaction, and file-size behavior. Minor gaps remain (bundle format/serialization, permission requirements) but the agent has enough to invoke it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning by tying include_files and max_file_bytes together and clarifying that workspace targeting is per-call only and does not change defaults.

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 (hosted project metadata as a portable bundle) and enumerates exactly which resource types are included (secrets, datasets, ontologies, transforms, functions, folders, files). It does not explicitly name or distinguish the closely related siblings bundle_import/bundle_diff, so it falls just short of the top tier.

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 word 'Export' suggests the direction, but the description never says when to choose this over whodb_platform_bundle_diff or whodb_platform_bundle_import, nor states prerequisites (e.g. requiring a resolved workspace).

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