Check Tech Stack

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

No annotations are provided, so the description carries the full burden. Beyond a vague hint that it looks for 'safety patterns and potential issues,' it says nothing about read-only behavior, what the check actually inspects (versions? known CVEs? code?), how thorough it is, or what a result contains.

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?

Single short sentence, front-loaded and waste-free, but the brevity is under-specification rather than efficiency. It is appropriately sized in form while failing to carry needed content.

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 eight parameters, no annotations, and no output schema, the description needs to carry far more weight than one clause can. Nothing explains what a 'check' produces, how results should be interpreted, or how the optional inputs change the analysis.

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 only 63%, and the description mentions no parameters at all, so the undocumented ones such as 'constraints', 'preferences', and the 'team_experience' enum are left ambiguous. For an 8-parameter tool, the description does nothing to clarify intent or accepted formats.

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 verb ('Check') and a resource ('technology stack'), so the general area is clear, but 'safety patterns and potential issues' is vague about what is actually evaluated. It offers no differentiation from siblings such as mcp_m7_safety_verify, mcp_m7_get_patterns, or mcp_m7_arch_advisor, which plausibly overlap.

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?

There is no statement of when to call this tool, when not to, or which sibling to prefer for adjacent concerns. An agent must guess whether this belongs before project setup, during review, or alongside safety_verify.

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