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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description usefully adds the auth/session requirement, that sign-in is free with one email, and the ordering guarantee that whole jobs lead the results. It stops short of describing output shape or how truncation actually behaves, but the added context beyond annotations is substantial.

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 critical auth prerequisite is correctly front-loaded, but the middle sentence ('how bid professionals actually run this work, from the weekly scan through...') is descriptive padding that consumes significant length without helping invocation. Caps-lock emphasis and parentheticals make it denser than it needs to be.

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, the description still conveys what the result contains (a library of playbooks, jobs first, compact vs full detail, truncation governed by max_chars) and fully covers the auth gate. An agent has enough to call it correctly; only the exact card structure 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 coverage is already 80%, and the description still adds real meaning: it explains that persona='consultant' surfaces the multi-client playbooks, that jobs always sort ahead of other rows (relevant to limit), and that session must be passed on every call in the conversation. These are usage semantics, not restatements, so it exceeds the baseline-3 case for high coverage.

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 the resource concretely ('The playbook library') and enumerates the coverage of the library (weekly scan, qualification, eligibility screening, specification reading, clarification, proposal skeleton), which tells an agent exactly what this listing contains. It also routes to the sibling get_workflow, distinguishing it from the single-item fetcher, though it never states the verb 'list' outright and relies on the title for that.

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?

It gives an explicit prerequisite chain (call connect_start(email) then connect_verify unless already signed in), an imperative selector condition ('READ A WORKFLOW BEFORE IMPROVISING A PROCESS'), a follow-up path ('Follow with get_workflow'), and a parameter-driven alternative view (persona='consultant' for multi-client playbooks). Nothing about when to reach for this tool is left to inference.

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