get_meta_download_columns

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions what the catalog contains (grouped, IPTC, custom meta fields, basic set), which adds useful context, but it does not disclose the output format (e.g., array structure), return size, pagination, or any side effects. For a read-only getter, the description is somewhat transparent but not fully explicit about the operation being non-mutating.

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 a single, compact sentence that is front-loaded with the core action ('Get the column catalog') and includes essential detail about the catalog's scope. Every word contributes meaning, with no fluff or repetition.

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 tool has no parameters and no output schema, the description provides a reasonable high-level explanation of what is returned (a column catalog with specific categories). It is complete enough for a simple getter. However, it could slightly improve by clarifying what a 'catalog' entails structurally (e.g., list of column names and metadata), but the provided detail is adequate for most users.

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?

The tool has zero parameters and a 100% schema coverage (empty schema). Baseline for 0 params is 4. The description does not need to add parameter details since there are none. It correctly implies that no input is required, which aligns with the schema.

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 clearly states the tool's function with a specific verb ('Get') and resource ('column catalog for metadata exports'). It distinguishes itself from sibling tools like list_meta_downloads by focusing on the column catalog, not the exports themselves, and even enumerates the included column sets (grouped + IPTC + custom meta fields + basic).

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 implies the tool is used to retrieve available columns for metadata exports, but it does not explicitly state when to use it compared to alternatives (e.g., before creating a meta download). It lacks an explicit 'when/when-not' recommendation, but the context is not misleading. The guidance is minimal but adequate for a simple getter.

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