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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the account-scoping constraint ("only data visible to the linked Market Brew account"), which is genuinely useful context, but says nothing about the char-based paging/truncation this export implies.

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?

Two short, front-loaded sentences with no filler; the scoping caveat is placed immediately after the trigger. It is efficient, though the first sentence spends words restating the name.

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 with offset/maxChars paging and no output schema, the description should convey that output is a character-limited text chunk and how to continue past maxChars. It omits this and never clarifies its relationship to list_deep_crawl_seeds, leaving an agent under-informed.

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?

Two of three params (offset, maxChars) are documented in the schema, but the required 'website' parameter has no schema description and the description does not compensate or explain its accepted formats (string or number). The description adds no parameter meaning at all beyond what the schema already says.

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 verb+resource (export crawl seed inventory) are present, but the first sentence largely restates the tool name and title rather than adding specificity. It does not distinguish this export from the sibling list_deep_crawl_seeds or export_deep_crawl_seed_attempts/errors, so an agent can't tell them apart from the description alone.

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?

"Use this when the user asks to export crawl seed inventory" is a trigger that merely echoes the name, offering no real when-to-use guidance. There is no mention of alternatives (list_deep_crawl_seeds, get_deep_crawl_seed) or conditions that select export over a list.

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