Save hours every week. This sop check tool toolkit gives you a battle-tested prompt and operating playbook for restaurant/brand growth. No setup, works in any LLM chatbot.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Optional user query to scope the analysis. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full disclosure burden, and it discloses nothing: no output shape, no rubric or criteria used for the 'check', no indication of whether results are pass/fail, scored, or narrative. The only content is promotional framing.
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?
Three sentences, none of which front-load the tool's function; the lead sentence is a benefit claim ('Save hours every week'). 'Toolkit' redundantly repeats 'tool', and 'battle-tested' is unearned filler.
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 annotations, no output schema, and a crowded sibling namespace of near-identical sop-* tools, the description needs to define the operation precisely. It instead reads as ad copy, leaving an agent unable to decide whether to call this, sop-audit-tool, or sop-gen-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 description coverage is 100% and the single optional 'query' param is documented in the schema as scoping the analysis, so the baseline of 3 applies. The description adds no meaning beyond the schema - it never says what the query should contain or how it narrows the check.
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 largely restates the name ('this sop check tool toolkit') and fills the rest with marketing ('battle-tested prompt and operating playbook for restaurant/brand growth'). It never says what 'check' actually means - validate an SOP against a rubric, score it, find gaps, or produce a report - nor how it differs from siblings like sop-audit-tool or sop-gen-tool.
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 when-to-use guidance at all. 'No setup, works in any LLM chatbot' describes deployment, not invocation context, and nothing distinguishes this from the ten other sop-* siblings (audit, gen, polish, reply, rewrite, sort, summary, tpl, write).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.