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

With no annotations, the description carries the full behavioral burden, and it only vaguely hints at deliverables ('includes the complete prompt, usage guide, and edge-case handling'). It does not say whether the tool returns static template text or generates content, whether anything is mutated, or what permissions/inputs are needed.

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 of marketing filler ('Turn expertise into output', 'professional results in minutes') with no substantive information front-loaded. The only concrete statement is the list of included assets, which is buried behind promotional phrasing.

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 and no output schema, the description needed to explain the return shape and when to pick this over the analyze/board/diag/formula siblings; it does neither and even introduces an off-domain audience. An agent cannot confidently decide between this and the other stock tools from this text.

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?

There is a single optional 'query' parameter at 100% schema description coverage, so the schema already explains scoping. The description adds nothing about what the query affects, but per the high-coverage baseline a 3 is appropriate.

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 never states what resource or domain this operates on; 'this stock tpl tool prompt pack' restates the name while the body talks about restaurant and brand teams, leaving the actual stock/template function ambiguous. It names no verb+resource pair and does not distinguish itself from the many stock-* siblings such as stock-analyze-tool or stock-formula-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 and no mention of alternatives, despite four adjacent stock-* tools in the sibling list. The only context offered is a vague audience claim ('restaurant and brand teams'), which is not a selection criterion an agent can act on.

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