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

Without any annotations, the description relies solely on text. It explains what the tool produces but does not disclose side effects, idempotency, or prerequisites beyond 'completed analysis.' There is no mention of whether the tool is read-only or modifies data, so behavioral transparency is moderate.

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 a single sentence that front-loads the main action and then provides a detailed list of outputs. While the list is somewhat long, it is dense and informative, without unnecessary filler. It could be more concise by grouping outputs, but it is not excessively verbose.

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 extensively lists outputs, which is useful, but it does not explicitly state that all prerequisite analyses must be completed, nor does it address error cases or return format. Given there is no output schema and no annotations, the description leaves some gaps about expected behavior.

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?

The only parameter is ideaId, and the schema description coverage is 0%. However, the description says 'on an existing idea,' which adds meaningful context that the parameter refers to an idea with completed analyses, going beyond the schema's simple type definition. This partially compensates 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 clearly states the tool's function: 'Run the Strategic Intelligence Engine on an existing idea.' It specifies the action (run), the resource (Strategic Intelligence Engine), and enumerates specific outputs (market landscape, competitive map, white space, etc.), making it easy to distinguish from sibling tools like score_idea or generate_competitor_analysis.

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 phrase 'on an existing idea' and 'synthesizes every completed analysis' implies the tool should be used after other analyses have been run. It provides clear context for when to use it, but does not explicitly mention alternatives or when not to use it, so it falls short of a perfect score.

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