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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully adds the account-scoping constraint ('only data visible to the linked Market Brew account'), but says nothing about the paged/character-offset nature of the export implied by offset and maxChars.

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 sentences, front-loaded with the trigger condition and no wasted prose. It is efficient, though the account-visibility sentence is somewhat tangential to 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?

For an export tool with pagination parameters and no output schema, the description should clarify return format and how offset/maxChars chunk the export; it does not. The account-visibility note is a partial substitute for return-value guidance.

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 50%: offset and maxChars have descriptions, while the two required parameters (website, seedId) have none. The description adds no parameter meaning at all, so it fails to compensate for the undocumented required inputs.

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-plus-resource ('export crawl seed attempt history'), so an agent knows what the tool does. It does not distinguish itself from close siblings such as list_deep_crawl_seed_attempts, export_deep_crawl_seeds, or export_deep_crawl_seed_errors, leaving the agent to infer the boundary.

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 attempt history' is an explicit trigger, but it is circular with the tool name and adds no decision criteria. No alternatives or when-not conditions are given, and the sibling list contains several near-identical export/list tools.

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