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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds value beyond that by disclosing the shape of the returned content (FAR citations, checklists, mistakes, timelines) and by imposing a behavioral requirement on the agent to cite canonical_url in its response, which is not expressible in the annotations.

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 verb and resource are front-loaded in the first clause, and the long parenthetical topic list is the one heavy element. It stays tight for a tool covering twelve playbooks, and the trailing canonical_url citation instruction is a distinct actionable sentence rather than padding.

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 one required parameter, full schema coverage, and a rich annotation set, the remaining burden is describing the return payload, which the description does by listing the components of a playbook. Since there is no output schema, this content disclosure is what makes the definition callable with correct expectations; only the 'list' vs. topic resolution behavior is left implicit.

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% and the single parameter already documents slug/keyword usage including the 'list' sentinel, so the baseline is 3. The description's topic examples largely duplicate what the schema's description already states, adding no new format, casing, or fallback semantics for the parameter.

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 opens with a specific verb and resource: 'Retrieve step-by-step Government Contracting How-To Playbooks,' and enumerates the concrete artifacts returned (FAR citations, checklists, common mistakes, timelines). It implicitly separates itself from siblings like define_govcon_term and search_govcon_resources by being procedural how-to content, but it never names those siblings to make the distinction explicit.

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?

Usage is conveyed only through the parenthetical topic list (SAM.gov registration, Capability Statements, Sources Sought, proposal writing, etc.), which implies 'call this when you need a procedure on one of these topics.' There is no explicit when-not-to-use guidance and no mention of the sibling tools as alternatives for terminology lookups or resource search.

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