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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral value by enumerating the return payload (simulation evidence, before/after example, metric breakdown, review guidance, previous feedback, failure patterns), letting the agent anticipate output despite there being no output schema.

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 opening sentence front-loads the core purpose, and the long enumerated list of returned sections is dense but earns its place by replacing a missing output schema. The trailing question list is slightly redundant but useful for intent matching.

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 read-only retrieval tool with no output schema, the description compensates by spelling out exactly what the briefing contains and what questions it answers. Auth nuance is left to the schema's customerId note, so coverage is strong though not exhaustive.

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 the schema already documents deploymentId, customerId and includeDiff. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb+resource ('Get PR Context') and immediately names the scope: a comprehensive reviewer briefing for a specific deployment/PR. The enumerated contents (issues fixed, what changed, simulation evidence, regression results, etc.) make it unambiguous which sibling this is versus read tools like get_review_case or get_verification_evidence.

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?

Provides concrete user intents ('tell me about this PR', 'should I merge this?', 'what does this fix?') and stresses 'one call', implying it consolidates what would otherwise be multiple lookups. It stops short of naming an alternative tool or an explicit when-not condition, so it is clear context without exclusions.

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