report_cards

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

No annotations provided; description only hints at rendering use case but does not disclose side effects, authentication needs, rate limits, or what 'individual card data' entails. The agent cannot infer safety or behavioral constraints.

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 is concise but omits critical details. Could include context about processing_id and output format without losing brevity.

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 no output schema and minimal description, the tool lacks sufficient information for correct invocation. Missing details about input semantics and return value structure.

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?

Input schema has 1 parameter (processing_id) with 0% description coverage. Description adds no explanation of what processing_id is, how to obtain it, or its format. Fails to compensate for schema gap.

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?

Description clearly states verb 'Get', resource 'individual card data from a report', and purpose 'for rendering'. It distinguishes from sibling tools like reports_list, reports_search, reports_view which operate on reports at a higher level.

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. Does not mention prerequisites, when not to use, or provide context about report processing state required.

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