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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds the configuration prerequisite, which is useful context, but never elaborates the destructive consequences (re-importing sessions, regenerating insights) that the fullResync param actually carries.

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?

Four short sentences with the core action front-loaded and the prerequisite immediately after. Efficient, with no meaningful padding.

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?

For a destructive ingest tool with no output schema, it covers the action, the source requirement, the discovery path, and mentions auto-sync configuration. Return behavior isn't described, but is minor given rich parameter docs.

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 the param descriptions themselves document defaults, bounds, and the destructive fullResync behavior. The description only gestures at source types and auto-sync settings, so it adds little beyond the schema; baseline 3 is appropriate.

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 (Sync) plus resource (runs) and the source class (external integration such as LangSmith/Langfuse). Clear enough to distinguish from read siblings like list_runs, though it does not explicitly contrast with the nearby sync_context_from_url.

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 a concrete prerequisite ('The integration must be configured first') and routes the agent to list_integrations to discover valid sources. Lacks an explicit when-not/alternative clause, so it stops short of a 5.

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