im_get_recon_summary

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

No annotations provided. Description only discloses output structure, not behavioral traits like read-only nature, default behavior for missing data, or any side effects. With no annotations, the description should cover these gaps.

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?

Two sentences with no redundancy. Front-loaded with purpose and output details. Every word earns its place.

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?

Adequately describes output (counts, match %) for a tool with 2 optional params and no output schema. Given tool simplicity, missing behavior for missing data is a minor gap.

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 coverage is 100% (baseline 3). Description adds meaning: explains that value_date defaults to today and recon_group is an optional filter. Provides format specification (YYYY-MM-DD) beyond 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?

Clearly states verb 'Get', resource 'reconciliation summary', and scope 'for a specific value date' with output details (matched/unmatched/exception counts, match % per group). Distinguishes from siblings like im_get_daily_summary.

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?

Implies usage when summary statistics for a date are needed, but lacks explicit guidance on when to use vs alternatives like im_get_daily_summary or im_get_match_statistics. No 'when not to use' or exclusion criteria.

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