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

With zero annotations, the description carries the full behavioral burden inclusively. It transparently reveals the output categories (OCEAN scores, ELM route, vulnerability flags, persuasion principle) and frames the action as an inference/mapping, implying a non-destructive read operation. It omits only minor details like processing limitations or error conditions.

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 primary purpose is stated in the first sentence, and the rest is organized into an action followed by a concise list of return fields. The common-use sentence adds context without redundancy.

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?

The description provides a clear purpose, the main inputs, the expected output fields, and a representative use case, all complemented by a 100%-covered input schema and an output schema. Missing only explicit failure/boundary conditions, which are secondary.

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 all three parameters are already well-described in the input schema. The description adds a practical usage hint (CRM Person/Account description) but doesn't meaningfully expand on any parameter beyond what the schema provides.

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 first sentence uses a specific verb ('infer') and object ('OCEAN personality profile') and immediately distinguishes the tool from generic analysis by stating it maps a free-text audience description into a structured psychological profile. This is clearly distinct from the sibling analysis tools.

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?

Provides clear context: applicable to personalized outreach, ad campaigns, sales messaging, and profiling CRM Person/Account data. However, it does not explicitly state when not to use this tool or compare it to potential alternatives.

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