export_public_card_query

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

With no annotations, the description should disclose behavior like whether this triggers a download, returns data directly, or requires specific permissions. It only says 'Export results' without any details on side effects or authorization needs.

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?

Single sentence, no redundancy. However, it is too brief for a tool with a complex input schema and many siblings. Could benefit from additional context without being verbose.

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 the complexity (nested parameter, multiple sibling export tools, no output schema), the description is insufficient. It does not clarify the relationship to other exports, the public nature of the card, or what the output contains.

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 has 0% description coverage for the nested 'input' parameter. The description does not explain what 'uuid' represents (likely the public card's UUID) or the significance of 'export_format' (csv/json/xlsx). No additional meaning is provided beyond the schema structure.

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?

Clearly states it exports results of a public card query in Metabase. The verb 'Export' and resource 'public card query' are specific. However, it does not distinguish between this and similar tools like export_card_query, but the name itself conveys the public aspect.

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?

No guidance on when to use this tool versus alternatives such as export_card_query or export_public_dashcard_query. Does not mention prerequisites (e.g., the card must be public) or when not to use it.

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