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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds genuinely new behavior: it must be answered from THIS user's targeting rather than a generic feature list, and it should offer five role-tailored follow-up questions. The empty-state branch is disclosed. Missing only anything about response shape/pagination, which is minor for a zero-param read.

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?

Front-loaded correctly: purpose first, then the triggering conditions, then the behavioral instructions. It runs long and the role examples (recruiter/seller question lists) are illustrative rather than essential, so a sentence or two could be trimmed without losing meaning.

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?

Complete for a zero-parameter, no-output-schema read tool: the description covers what is returned, when to call it, how to personalize the answer, what to do when targeting is empty, and which sibling handles the save. Nothing an agent needs to invoke or follow up correctly is absent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of 'industries, locations, company sizes, and buying signals' usefully previews the shape of the returned object even though no schema details are needed.

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 and resource and enumerates what the preferences contain (industries, locations, company sizes, buying signals), which distinguishes it cleanly from update_targeting_preferences and from the search_* siblings. An agent reading only the first sentence knows exactly what comes back.

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 an explicit priority rule ('Call this FIRST when the user asks what Fundz can do ... or opens with a vague question') plus named trigger conditions, and routes the empty-targeting case to the specific alternative: update_targeting_preferences. When-to-use, when-empty, and the alternative are all spelled out.

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