Strategic Flow MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only lists topics; it does not state that this is a non-destructive query operation, what the response format is, how errors or unknown topics are handled, or that an api_key is required for invocation (auth is only discoverable in the schema property description). For a tool with zero annotation coverage, this is a notable gap.

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?

A single sentence with zero filler, front-loading the verb and resource before the topic enumeration. There is no redundancy or wasted wording; the description is appropriately terse for a simple query tool.

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 simple two-parameter Q&A tool with no output schema and no annotations, the completeness bar is lower, and the description adequately covers what topics are in scope. However, it omits what constitutes a well-formed question, the expected response shape, and confirmation that this is a read-only operation. The api_key hint implies authentication needs but is not stated in the description itself.

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%, so the baseline is 3. The description simply restates the topic list already present in the 'question' parameter description almost verbatim, adding no syntax, format, or quality guidance beyond the schema. The api_key parameter is fully documented in the schema. The description adds minimal value over the schema, so it sits at baseline.

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 uses a clear verb ('Ask') and a specific resource (Strategic Flow knowledge), and enumerates its topic domains: email conversion, funnel friction, Decision Friction Model, Strategic Flow Tech services. It informally distinguishes itself from the sibling audit_email by framing itself as a Q&A tool, though it doesn't explicitly name the alternative. Not a tautology and the scope is crisp.

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?

Usage is implied: agents should use this tool when they have questions about the listed domains. However, there is no explicit when-to-use versus alternative guidance, no exclusions, and no statement of what audit_email should be used for instead. For a tool with only one sibling, naming the trade-off would be meaningful, but the category difference (ask vs. audit) is partially inferable.

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

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

No annotations are provided, so the description carries the full burden. 'Audit' plus 'return a diagnosis' implies a non-mutating analysis, which is useful behavioral context. However, it does not disclose external API dependencies implied by the api_key parameter, potential cost, latency, or data-handling behavior, which an agent would benefit from knowing.

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?

A single sentence with no wasted words: it names the target (SaaS lifecycle email), the method (7-point Decision Friction Model), and the return value (structured diagnosis). Everything is front-loaded and readable at a glance.

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 presence of an output schema and 100% parameter coverage means the description need not explain return values or parameter details. The main gaps are usage guidance (no alternative routing, no when-not-to-use) and behavioral context such as external API/cost implications. Reasonably complete for a moderate-complexity tool, but with clear gaps.

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 every parameter (including the three required ones) already has a meaningful description. The tool description adds no per-parameter detail, but with full schema coverage the baseline of 3 applies. The mention of the 7-point model only vaguely communicates how body/desired_action feed the analysis.

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 ('Audit a SaaS lifecycle email') and names the analytical lens (7-point Decision Friction Model) plus output form ('structured conversion diagnosis'). This clearly separates it from the generic sibling ask_strategic_flow, though the description never names that sibling explicitly.

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 implies when to use it: whenever a SaaS lifecycle email needs conversion auditing. However, it gives no explicit when-to-use versus ask_strategic_flow, no exclusions, and no statement about what situations are inappropriate for this tool. The usage context is implied rather than stated.

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