get_embed_card_query_format

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

With no annotations, the description must disclose behavioral traits. It states it 'gets query results' but does not indicate whether the operation is read-only, what happens on invalid tokens, rate limits, or whether it returns raw data or triggers downloads. This is insufficient for safe agent decision-making.

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 concise sentence that efficiently conveys the main purpose. It is front-loaded with key information, but could include more detail without becoming 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 complex nested parameter structure, lack of output schema, and many similar sibling tools, the description is incomplete. It does not explain the return format (e.g., file content vs. URL) or provide context about the embedding mechanism, leaving the agent uncertain about behavior.

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 parameter-level meaning. The nested 'input' object is not explained, and the parameter descriptions ('JWT embed token', 'Export format') are minimal. The description fails to compensate for the absent schema documentation.

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 action ('get'), the resource ('query results for an embedded card'), and a qualifier ('in a specific export format'), making the purpose specific and unambiguous. However, it does not explicitly differentiate from closely related siblings like get_embed_card_query or export_embed_card_query.

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 provides no guidance on when to use this tool versus the many similar sibling tools (e.g., get_embed_card_query, export_embed_card_query). It lacks any when/when-not information or prerequisites, forcing the agent to rely solely on the name.

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