market_export

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

No annotations are provided, so the description must cover behavioral traits. It only states the export action and tier requirement, but does not disclose side effects, how data is returned, or any destructive potential. Minimal transparency.

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 very short (one sentence plus a requirement), which is concise but at the cost of missing critical details like parameter explanations and usage context. It is front-loaded with '[Intel]' tag, but overall under-specified for its complexity.

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 4 parameters with no schema descriptions, no output schema, and no annotations, the description fails to provide sufficient context. It does not explain what 'data moat' is, what each parameter does, or what the output looks like. Highly incomplete.

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%, and the description adds no information about the four parameters (country, line, format, limit). It mentions CSV/JSON formats but does not link them to the format parameter or explain other params. Parameter semantics are completely missing.

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 'Export data moat as CSV or JSON', which clearly indicates the tool's action (export) and output formats. It distinguishes from sibling tools like market_search by focusing on export functionality, though 'data moat' is somewhat vague. Overall, purpose is clear.

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 only mentions a tier requirement ('Requires starter tier or above'), but gives no guidance on when to use this tool versus alternatives like market_intel_brief or market_stats. No when-to-use or when-not-to-use context is provided.

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