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

Annotations declare destructiveHint=true, openWorldHint=true and idempotentHint=true, but the description discloses none of this. Most importantly, it never warns that inputs and prior-agent context are sent to an external inference provider (the required consentExternalProcessing flag) or that a confirmed payment invoice may be required — material facts an agent cannot infer from a single marketing sentence.

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?

One front-loaded sentence with zero waste, but it is sized for a landing page rather than a tool definition. Conciseness here comes at the cost of omitting anything operationally relevant.

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?

This is a complex tool: six parameters, a nested required inputs object, a consent gate for external processing, and a destructive annotation — with no output schema to lean on. A single sentence is far too thin to prepare an agent for those obligations, though the relatively rich schema keeps this from being a total 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 67% and the nested inputs object is well documented field-by-field, so the schema carries most of the load. The description itself adds no parameter meaning whatsoever — nothing about sourceRunIds/sourceFields pulling prior artifacts or about how idempotencyKey behaves on retries.

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 concrete verb and artifact: turning a category brief into an RFP draft with requirements and weighted evaluation criteria. That is enough to tell it apart from evaluation/scoring tools, but it never mentions the sibling xrfi-drafter or the rfp_to_bid_review workflow, so the RFP-vs-RFI boundary is left to inference.

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?

There is no when-to-use guidance, no prerequisite (e.g. needing prior run IDs), and no mention of alternatives such as xrfi-drafter or the negotiation workflows. The agent must guess when this is the right entry point versus drafting an RFI or going straight to bid review.

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