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

Annotations already establish that this is a mutating, non-idempotent, open-world operation. The description goes further by disclosing the 20-second freshness dedup window, the fact that recently-fetched accounts are skipped, and the exact return shape. This adds meaningful behavioral detail beyond the annotation flags.

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?

Three dense sentences carry action, scope, dedup behavior, return format, and a follow-up recommendation. There is no filler, and the most important action is front-loaded.

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 documents the return object, the dedup constraint, and the follow-up tool, which is substantial for a tool with no output schema. It is slightly incomplete on parameter behavior and error semantics, but for a refresh action with one obvious parameter, it is well covered.

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 0%, and the description does not explicitly explain how workspaceId behaves, whether it is optional, or what happens when it is omitted. The word 'workspace' in the description loosely implies the parameter's role, but the description does not compensate for the missing schema documentation.

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 opens with a specific verb and resource: 'Trigger an inbox refresh for all LinkedIn accounts in the workspace.' It clearly explains the polling and routing behavior, and the follow-up reference to list_inbox_conversations distinguishes it from reading conversations directly.

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 clear context for when this tool is relevant and explicitly routes to campaignstack_list_inbox_conversations after the refresh. It does not state when not to use it or compare it with other refresh-related tools, but the context is strong enough for an agent to select it appropriately.

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