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

Annotations already flag non-read-only, non-idempotent, destructive and open-world behavior; the description adds genuinely new context the annotations lack: plan entitlement and shared fair-use budget consumption. It could go further by saying the result is persisted/attached to the prompt and whether regeneration overwrites it.

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 sentence, front-loaded with the action and resource, with the constraints in parentheses. Nothing extraneous.

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?

No output schema exists, so the description should say more about what a 'brief' contains and whether the call is repeatable/billed each time. For a budget-consuming, destructive-flagged generation tool with an undocumented required parameter, this is adequate but with clear gaps.

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 50%: siteId is documented but queryId has no schema description. The phrase "for a tracked prompt" hints that queryId is a prompt identifier, but it never says where to get that id, leaving the required parameter's provenance implicit.

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?

Specific verb+resource: "Generate an AI content brief for a tracked prompt" tells the agent exactly what is produced and the scope (a single tracked prompt). It doesn't explicitly distinguish itself from similarly-named siblings like get_evidence or start_deep_scan, so it falls short of a 5.

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?

Adds real gating information — Pro plan requirement and that it draws from the account's generation fair-use budget — which implies 'use sparingly.' However, it never states prerequisites such as obtaining queryId from list_prompts, nor when to prefer this over other evidence/scan tools.

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