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

Annotations already declare a non-destructive, idempotent write in a closed world. The description adds meaningful lifecycle context: the draft is private and unverified, requires real company confirmation before authority, and needs independent review/publication permission before search visibility.

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 description is two sentences and front-loads the purpose before the lifecycle constraints. The second sentence is dense and slightly awkward ('before authority and independent review/publication permission'), but there is little wasted text.

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?

For a complex write tool with nested objects and no parameter descriptions, the description adequately covers the tool's gating and privacy posture but does not compensate for the missing parameter semantics. It is minimally complete rather than fully sufficient.

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 0%, so the description must clarify parameters, but it only indirectly references the consent requirement. It adds no meaning for idempotency_key, referral_source, or the nested profile fields, leaving most parameter semantics to inference from the raw schema.

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 states a specific verb (Submit) and resource (manufacturer draft), with clear qualifiers: explicitly consented, private, and unverified. It does not differentiate from the sibling update_manufacturer_draft or register_manufacturer_interest, 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?

The description gives prerequisites such as real company confirmation and publication permission, but it never says when to use this tool versus create_agent_conversation, register_manufacturer_interest, or update_manufacturer_draft. It provides condition-level context but no alternative routing guidance.

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