Check Operational Integrity

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

Annotations already indicate readOnlyHint: true, so the description's 'Evaluate' aligns. It adds context about checking safety for multiple operations, but does not elaborate on behavioral traits (e.g., what checks are performed, what happens if state is unsafe). With annotations present, the description adds modest value.

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 sentence that front-loads the core purpose, with no unnecessary words. It is concise and well-structured.

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 5 optional parameters, no output schema, and annotations providing readOnlyHint, the description covers the tool's overall purpose. However, it does not detail what 'operational integrity' entails or the return format, but the schema and annotations fill some gaps. Overall, it is sufficiently complete for a safe read-only check tool.

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 100%, so each parameter is documented. The tool description does not add extra meaning beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb 'Evaluate' and clearly identifies the resource as 'current repo state' with explicit scope for PR, merge, release, and publish operations. This distinguishes it from sibling tools that focus on specific actions (e.g., get_branch_governance, approve_protected_action).

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 implies usage before PR, merge, release, and publish operations, but lacks explicit when-to-use or when-not-to-use guidance compared to the large set of sibling tools. No alternatives are mentioned.

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