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

Annotations already mark this as a write/destructive, non-idempotent tool, and the description adds meaningful context: the write-tier approval flow, 'the card is the yes — do not re-ask in chat,' and content guardrails such as 'never invents faith prose' and 'never invent from empty corpus.' There is no contradiction with 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 action is front-loaded in the first sentence, and each subsequent clause earns its place: alternatives, trigger conditions, approval workflow, and safety guardrails. It is dense but not bloated, and the structure makes it easy for an agent to extract the key constraints.

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?

Even without an output schema, the description defines what gets created, when the tool should be used, what approvals may be needed, and what to avoid. It gives an agent enough context to select, invoke, and interpret the result correctly.

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 baseline is 3. The description reinforces the count behavior ('Default count is 1 — do NOT bulk-fill the queue'), but the parameter-level meaning is already well covered by the input schema, so the description adds limited additional semantic value.

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: 'Mint the NEXT content angle(s) from the company's corpus into content_ideas + Command Center cards.' It states the exact output artifacts and clearly separates this tool from reading-oriented siblings by saying it is only for when a human-facing card is needed.

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 guidance is explicit: 'For day-to-day drafting, prefer list_knowledge / read_knowledge (or list_corpus_inventory)' and 'Use promote only when a human-facing card is needed (weekly queue, Held post, operator asked).' It also warns against bulk-filling the queue and tells the agent to call it on the first clear ask rather than re-asking.

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