Check whether one tool is needed

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered without the description. Beyond that, the description adds only the idea of a threshold comparison; it does not explain the scoring scale, what happens when options is omitted (is there a default threshold?), or what the verdict looks like. Useful context, but thin for a decision tool with no output schema.

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?

Two tight sentences, front-loaded with the action and followed by the usage trigger. No filler, though a single added clause about the threshold or return value would have cost nothing and closed real gaps.

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?

There is no output schema and the description does not describe the response beyond "whether it clears its threshold" — the score itself, its range, and any explanation field remain unknown. Combined with the undocumented user_query and options parameters, an agent still has to guess at core call semantics for what is a three-parameter, nested-object tool.

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 33%: only tool_id is documented in the schema, while user_query and the nested options.threshold have no descriptions. The description hints at a threshold but never says what it is applied to, how it defaults, or what user_query should contain (a raw user utterance? a summarized task?). With low coverage the description needed to compensate and largely does not.

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 names a specific verb and resource ("Score a single tool against a task") and states the output shape in prose ("say whether it clears its threshold"). The word "single" implicitly contrasts with the batch-oriented sibling systemone_decide_tools, but it never names any sibling, so the differentiation is suggestive rather than explicit.

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?

It gives a usable trigger condition: use when the agent is unsure whether one specific MCP tool is worth calling. That is a clear positive case, but there is no when-not guidance and no mention of the alternative (systemone_decide_tools / systemone_get_catalog) for tasks involving multiple tools.

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