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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely non-obvious behavioral context beyond that: this tool does not emit the finished draft, it returns a drafting brief derived from award criteria, word limits and user facts, which is essential to using the result correctly.

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?

Front-loaded with the trigger scenario, then the return value, then the follow-on instruction, then the exclusions. Every sentence carries distinct information and there is no filler.

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?

An output schema exists and annotations cover safety, so the description needn't explain the return shape, yet it still summarizes the brief's basis (award criteria, word limits, facts), which is helpful. Coverage of the multi-step draft workflow relative to its sibling tools is the only gap.

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% with descriptions and an enum for section, so the schema already carries the parameter burden. The description alludes to word limits and the user's facts (word_limit, notes) and lists the section values, adding only marginal 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?

States a specific verb and resource — drafting part of a response to a public tender — and enumerates the concrete artifact types (quality answer, social value, method statement, case study, etc.). It clearly separates itself from non-bid tools, but does not distinguish itself from close siblings such as start_bid_draft, continue_bid_draft, or rewrite_bid_answer, which could leave the agent uncertain which of the draft-family tools to pick.

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?

Gives an explicit 'use this when' trigger plus concrete 'do not use for' exclusions (job applications, grant applications, private-sector sales proposals), and hints at the follow-on action ('Write the draft from the brief'). Missing only an explicit routing statement to sibling tools for the alternative steps of the draft workflow.

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