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

No annotations, so the description carries full burden and does so well: it discloses the two-step email/pay-link flow, that nothing is charged automatically, and that the profile stays private until payment. It also implies the consent requirement, all behavior beyond what the schema conveys.

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?

Three sentences, front-loaded with the core action and followed by workflow and privacy/charge clarifications. Dense but every sentence earns its place; minimal waste.

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?

Covers the write action, required inputs, the email/pay-link mechanism, privacy posture, and no-auto-charge behavior. Lacks an output schema, but the description adequately implies the response is a pending/pay-link-issued state without needing to enumerate return fields.

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 100%, so every parameter is already documented in the schema. The description reinforces the required-fields precondition but adds no per-parameter semantics beyond what the schema provides; baseline 3 applies.

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+resource ('Submit a business to be listed') and uniquely identifies the target site. Clearly distinct from siblings like search_companies or read_company_profile, which are read operations on an existing directory.

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 a clear precondition ('Collect all required fields from the user first') and describes the activation flow. It doesn't explicitly say when NOT to use it or name a sibling alternative, so it stops short of 5.

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