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

Annotations declare this is a non-read-only, non-destructive, non-idempotent write scoped to the local system. The description adds value beyond them by disclosing the auth requirement ('Admins only') and the actual effect (opening a pull request in the connected repository), plus the failure precondition that explains why a retry is needed. It does not explain the non-idempotency consequence (e.g., possible duplicate PRs).

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 tight sentences: the action and its precondition come first, the permission gate second. No filler, nothing restating the title.

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?

For a one-parameter mutation with no output schema, the definition covers purpose, precondition, and authorization, which is enough to call it correctly. It leaves minor gaps around what a successful retry returns and whether repeated retries risk duplicate pull requests, but nothing essential is missing.

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% and the single parameter already documents that the id comes from list_training_proposals. The description adds no syntax, format, or sourcing detail beyond the schema, so the baseline 3 applies for a param fully carried by structured data.

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 names a specific verb ('try again to open the pull request'), the resource (approved guidance published to the connected repository), and the precise precondition (a prior publication attempt failed). This cleanly distinguishes it from approve_training_proposal and dismiss_training_proposal, which operate on proposals rather than on a failed publish step.

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 trigger condition is explicit: use this when publication to the connected repository has already failed and you want to retry. 'Admins only' adds a role gate. It stops short of naming a pre-step (e.g., 'requires the proposal to already be approved') or an alternative, so it is clear context without full routing guidance.

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