export_items

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

With no annotations provided, the description carries the full disclosure burden and does well: it states the Pro license requirement and explicitly explains that an invalid license yields an upgrade message rather than a confusing error. It does not mention rate limits or pagination, but the license-gate behavior is the most important non-obvious trait.

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 core function is front-loaded, and the license explanation is useful context rather than filler, but the free/Pro split commentary is slightly longer than strictly necessary. Overall it is well-organized and each sentence contributes to correct invocation.

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?

Given there is no output schema, the description compensates by listing the exact returned fields, formats, filtering option, and license failure mode. Minor gaps remain, such as whether the topic filter is exact-match or case-sensitive, but the definition is complete enough for an agent to use it correctly in most cases.

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 0%, so the description must compensate. It explains both parameters: 'topic' as an optional filter and 'format' as json or csv text. That is sufficient to invoke correctly, though exact enum values or default behavior are not restated in the description.

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 specifies the exact operation ('Export items'), the fields returned, the supported formats (json/csv), and the optional topic filter. This clearly distinguishes it from siblings like add_item and get_due_items, which are about adding or retrieving due items rather than exporting the whole collection.

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?

It gives clear context: this is the paid-tier bulk export/backup tool, optionally scoped to one topic, while the 4 core tools remain free. It does not explicitly name sibling alternatives or when not to use them, but the positioning and verb make the use case evident enough.

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