meeting_prep_process_contact_research

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the processing actions but fails to disclose side effects, permissions required, idempotency, or that it likely stores results in a variable (given the output_variable_name parameter). The description lacks clarity on whether the tool modifies state or is safe to call multiple times.

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 a single sentence that efficiently conveys the tool's purpose. It is front-loaded with the main verb and resources, with no unnecessary words or repetition.

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 the tool is part of a meeting prep pipeline with numerous siblings and no output schema, the description should explain its role in the pipeline and that it stores output to a variable. It omits that the output is likely saved via 'output_variable_name', and doesn't specify that it should be used after contact_research and before assembly. The description is insufficient for an agent to fully understand its integration.

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 100%, and each parameter has a basic description (e.g., 'The results from the Contact Research action.'). The tool description itself does not add extra meaning beyond the schema. Baseline of 3 is appropriate because schema already documents parameters, though descriptions are minimal.

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 clearly states the tool's function with specific verbs (processes, identify, build, calculate) and resources (contact research results, primary contact, profiles, quality scores). It distinguishes from sibling tools like 'contact_research' which likely gathers raw data, while this tool processes that data.

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 provides no guidance on when to use this tool versus its many siblings, such as whether it should be called after contact_research or before assembling a meeting document. No explicit context or alternative recommendations are given.

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