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

The description goes well beyond the destructiveHint=true annotation: it discloses async server-side execution, the incremental read scope, the polling handshake with prism_studies_get, credit consumption, and two non-obvious return states (upToDate no-op, needs_confirmation). No contradiction with the mutation-oriented annotations.

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?

Front-loaded with the action and its incremental nature, then layers the async/polling contract and edge cases without a wasted clause. Dense but every sentence carries operational value.

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?

With no output schema, the description carries the full burden of describing return behavior and does so thoroughly (phase, upToDate, needs_confirmation) plus the async completion protocol and cost implication. An agent has everything needed to invoke and correctly follow up.

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 50%, with workspace and reanalyzeAll documented in the schema while studyId and approvalId are undocumented everywhere. The mention of needs_confirmation implicitly gestures at the approval flow but the description adds no direct semantics for those two parameters, so it only partially compensates.

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 and resource ('Kicks the theme analysis') and immediately qualifies the scope as incremental, so an agent knows exactly what work is triggered versus a full re-read. It is distinguishable from siblings like prism_studies_get and prism_studies_results.

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 concrete follow-up guidance: it returns immediately, so re-read prism_studies_get and poll until insights stop reporting an active run. It also flags upToDate:true as a healthy no-op and warns that needs_confirmation may be returned. It stops short of explicitly contrasting incremental mode against the reanalyzeAll parameter as an alternative.

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