analyze_github_project_reconciliation

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results require an authorized Project and are 'evidence-backed', but it says nothing about pagination via 'first', how archived items are handled, or what the mismatch report contains.

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?

A single, front-loaded sentence with no filler; the core verb and resource lead. It is efficient but arguably too terse given the parameter surface it must support.

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?

With no output schema and 7 undocumented parameters, the description should explain the shape of the reconciliation report and the meaning of key inputs, but it does neither. An agent cannot confidently invoke it with non-default parameters.

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 0% across 7 parameters, so the description carries full burden and largely fails. Only 'Project Status' loosely hints at statusFieldName/completedStatusNames, while first, includeArchived, and reportDoneButNotMerged are entirely undocumented in both schema and description.

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 states specific resources (Pull Request merge state, Project Status) and a concrete action (compare and surface workflow mismatches), so an agent knows this is a reconciliation/audit analyzer. However, it does not distinguish itself from the similarly named sibling analyze_github_project_state_gaps or compare_github_project_state_checkpoint, so the agent must guess which analyzer applies.

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?

There is no guidance on when to use this tool versus the many sibling analyzers (state_gaps, compare_state_checkpoint, get_project_snapshot). The only hint is the implied audit use case from 'reconciliation', which the agent must infer.

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