bulk_export

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

No annotations are provided, so the description carries the full burden. The description is only 18 characters and reveals nothing about potential side effects, output format details, size limitations, or whether this is a read-only operation. The include_private parameter hints at access control implications, but the description doesn't address data sensitivity or authorization requirements.

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 efficient sentence with no fluff. It's appropriately minimal for the tool's scope, though it might err on the side of being too terse given its importance as a bulk operation.

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 an export tool that could dump all user data, the description is notably thin. It doesn't mention output format specifics beyond 'JSON', doesn't explain what the include_private flag actually protects/privacy implications, and doesn't note that no output schema exists so the return value format is entirely undefined. The tool name alone suggests bulk behavior but nothing about performance, pagination, or result structure.

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 both parameters (tables and include_private) are already documented in the schema. The description adds little beyond '全データまたは指定テーブル' which just restates the tables parameter concept. Baseline 3 applies since schema does the heavy lifting.

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 states '全データまたは指定テーブルのJSON一括エクスポート' (bulk export all data or specified tables as JSON), which is a clear verb+resource purpose. However, it doesn't distinguish itself strongly from sibling bulk_import or batch_operations beyond being the export counterpart.

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 implies it exports all data or selected tables, giving some usage context. It doesn't explicitly state when to use this vs alternatives, nor does it mention exclusions or prerequisites, though the schema's table parameter provides some guidance on scoping the export.

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