run_public_card_pivot_query

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

With no annotations, the description should disclose behavioral traits. It only says 'Run a pivot query' but doesn't clarify if it is read-only, modifies state, requires authentication, or has any side effects. The agent cannot infer safety or preconditions.

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 concise at one sentence but lacks structure. It is front-loaded with the purpose, but misses crucial details. Every word is necessary but insufficient for usability.

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 lack of annotations, no output schema, a complex nested parameter, and no parameter documentation, the description is severely incomplete. The agent cannot effectively use this tool without additional context.

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 description offers no parameter information. The input schema has nested objects (uuid, parameters), but 0% schema description coverage means the schema itself lacks documentation. The description fails to compensate, leaving the agent without guidance on what 'uuid' and 'parameters' mean or how to use them.

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 it runs a pivot query for a public card, specifying the resource and action. However, it doesn't elaborate on what a pivot query entails, which may be ambiguous for some agents. It distinguishes from siblings like run_dashcard_query by mentioning 'public card'.

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 is provided on when to use this tool versus alternatives (e.g., run_embed_card_pivot_query, run_dashcard_query). No preconditions or when-not-to-use context is given, leaving the agent without decision support.

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