Refresh Contact List

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

With no annotations, the description provides some behavioral context (re-evaluates criteria, materializes members) but fails to disclose potential side effects like whether the refresh is synchronous, if it triggers notifications, or if specific permissions are required. It is informative but incomplete.

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 two sentences long, front-loaded with the main action, and every sentence adds value. There is no extraneous information, achieving excellent conciseness.

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 covers the core behavior (re-evaluate and materialize) and mentions 'dynamic' list. However, it lacks information about return values (no output schema) or whether the operation is asynchronous. Still, it is fairly complete for a refresh tool.

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 the schema already describes the 'idOrSlug' parameter. The description adds no additional meaning or format beyond what the schema provides, meeting the baseline expectation.

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 verb 'Trigger a refresh' and identifies the resource as 'a dynamic contact list'. It further explains the action by mentioning re-evaluation of criteria rules and AI prompts, making the purpose specific and distinct from sibling tools like update or create.

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 implies usage for refreshing dynamic lists but does not explicitly state when to avoid using this tool or how it differs from alternatives like neuron_update_contact_list (which modifies rules) or neuron_get_contact_list (which merely retrieves). No exclusions or prerequisites are mentioned.

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