Terraform Registry MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what content is fetched (documentation sections) and the return format (dictionary in markdown), but does not mention potential limitations like rate limits, authentication requirements, error conditions, or whether this is a read-only operation. It adds some behavioral context but leaves gaps for a tool with no annotations.

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?

The description is well-structured and appropriately sized. It starts with a clear purpose statement, then lists the fetched documentation sections in bullet points, followed by parameter explanations and return format. Every sentence adds value with no wasted words, and information is front-loaded effectively.

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?

Given the tool's moderate complexity (4 parameters, no annotations, but with output schema), the description is mostly complete. It explains parameters thoroughly and describes the return format, though the output schema existence means it doesn't need to detail return values. However, without annotations, it could benefit from more behavioral context about limitations or prerequisites.

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?

With 0% schema description coverage, the description fully compensates by explaining all 4 parameters with clear semantics and examples. It defines namespace, name, resource_name, and version (including default value), adding essential meaning beyond the bare schema. This exceeds the baseline expectation when schema coverage is low.

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 clearly states the specific action ('Get detailed documentation') and target resource ('for a specific provider resource'), distinguishing it from siblings like get_provider_docs (general provider docs) or get_provider_data_source_docs (data source docs). It includes a verb+resource combination that is precise and unambiguous.

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 usage context through the parameter explanations and return format, but does not explicitly state when to use this tool versus alternatives like get_provider_docs or get_provider_data_source_docs. It provides clear context about what documentation is fetched, but lacks explicit when/when-not guidance relative to siblings.

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