reconcile

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It mentions the action but does not state whether this is read-only, whether it modifies data, what it returns (e.g., a report, pass/fail), or how mismatches are handled. This is a significant gap for a tool with no other metadata.

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 states the tool's function without unnecessary words or repetition. It is front-loaded and immediately conveys the core purpose.

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?

The tool is simple (zero parameters) and has no output schema, so the description could be minimal, but it omits the outcome or result format. It does not say what the reconciliation produces (e.g., a report, a status), which would be helpful for the agent to know what to expect after invocation. This makes it slightly incomplete but acceptable for a basic validation action.

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 tool takes zero parameters, so schema coverage is vacuously 100%. The baseline for zero parameters is 4, and the description adds no parameter-specific information because none is needed. It provides the tool's purpose without needing to describe arguments.

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 a specific action ('Reconcile') with a defined resource ('each entity's fetched row count') and method ('against an independent COUNT(*) of the source'). This distinguishes it from sibling tools like query and check_query, which focus on data retrieval, not validation.

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. The description only says what it does, not the context (e.g., after running a sync) or why it should be used instead of check_query or query. The user is left to infer that reconciliation is a validation step.

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