Prep for Person (Communication Strategy)

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

Discloses that profiling is passive and local, the four-color shell is a mapping not a clinical diagnosis, and tool returns suggestions only—never manipulation. Also notes error handling for missing page slug. No annotations exist, so description carries full burden.

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?

Well-structured with clear sections (What it does, When to use/not use, Returns, On error). Each sentence is purposeful and concise, no wasted words.

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?

Given two parameters, no output schema, and no annotations, the description provides thorough context: purpose, usage boundaries, return type, ethical note, and error guidance. Fully adequate for the tool's complexity.

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% with both parameters described. Description adds extra context like 'toward a specific goal' for the optional goal parameter, which enriches understanding beyond 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?

Clearly states the tool prepares a goal-conditioned communication strategy from a passively-inferred profile. Uses specific verb 'prepare' and resource 'communication strategy'. Distinguishes from sibling `get_entity_profile` which provides raw facts.

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?

Explicitly states 'When to use: before talking to someone' and 'When NOT to use: raw facts; use get_entity_profile/query'. Provides clear guidance on alternatives.

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