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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds little behavioral context beyond saying the guide is 'exact', but it does not contradict the annotation and does not need to disclose side effects. It lacks any mention of response behavior or caching, but with annotations covering safety, this is adequate.

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, compact sentence that front-loads the resource type and immediately enumerates valid options. No filler words, and every segment adds value.

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 parameterized lookup with an output schema, the description is largely sufficient. It identifies the valid inputs and purpose. It could mention that the parameter is optional with default fastmcp, but that is already in the schema, and the output schema covers return expectations.

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 0% and the schema provides no description for the 'framework' parameter, so the description must compensate. It lists all accepted values (fastmcp, python, typescript, skybridge, langgraph, crewai, generic, openclaw, widgets), which is meaningful. It does not explain what each value returns or the default, but the enum-like list is a strong addition.

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 operation ('get integration guide') and the exact resource ('guide for a stack'), with a clear enumeration of supported stack values. It is immediately distinguishable from siblings like search_mcps or verify_integration, which serve different purposes.

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 this tool (when you need an integration guide for one of the listed stacks), but it does not explicitly state when not to use it or reference alternatives. There is no conflict with siblings, but the guidance is implicit rather than explicit.

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