generate_reconciliation_report

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

No annotations provided, so the description carries the full burden. It states the tool 'queries each entity,' implying a read operation, but does not explicitly confirm read-only behavior or disclose other traits like rate limits or authentication requirements.

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?

Description is two succinct sentences with front-loaded purpose and no superfluous information. Every sentence contributes to understanding the tool's function and value.

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?

While the output schema exists (covering returns), the description omits details about how to use auth parameters and whether expected_counts is required. The cutover validation context is helpful but incomplete for effective invocation.

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 only 20%, yet the description does not add meaning for parameters like data_center, auth_user_id, auth_password, or expected_counts beyond the schema. The 'comparing expected vs actual' hint partially covers expected_counts but leaves others unaddressed.

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 the tool generates a reconciliation report comparing expected vs actual record counts, with specific verb and resource. Mentions cutover day validation, distinguishing it from siblings like reconcile_data by focusing on a specific use case.

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 specifies the tool is 'Essential for cutover day validation,' providing context for when to use it, but it lacks explicit guidance on when not to use it or direct comparisons to sibling tools like reconcile_data.

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