analysis.update

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

With no annotations provided, the description carries full behavioral disclosure burden but only states it is async. It does not disclose side effects (e.g., whether it triggers analysis on current session or a specific one), progress reporting, cancellation behavior, or result delivery mechanism, leaving significant ambiguity.

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 words is extremely concise, but borderline under-specified. There is no waste, but the brevity omits critical context. Front-loading is inherent due to short length.

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 has one parameter, no output schema, and 0% schema description coverage, the description is incomplete. It does not explain return behavior (does it return a task ID?), error states, or how results are consumed. Among complex siblings, this leaves agents guessing.

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% with one required parameter 'session_id' described only as a string type. The description adds no meaning about session_id's purpose (e.g., target session for update) or format, failing to compensate for the lack of 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 'Trigger async analysis update' provides a verb and resource but is vague. It does not specify what 'analysis update' refers to or what data it processes. Among siblings like analysis.update_and_wait, analysis.status, and analysis.progress, the description fails to distinctly position this tool.

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?

No guidance on when to use this tool vs alternatives like analysis.update_and_wait, analysis.abort, or analysis.set_hold. The description lacks context on prerequisites (e.g., requires an open session), when async is preferable, or why not to use synchronous options.

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