Terraform Registry MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information (implying read-only), but doesn't mention potential errors (e.g., if the provider doesn't exist), rate limits, authentication needs, or the format of the returned dictionary. This leaves significant gaps in understanding how the tool behaves in practice.

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 with clear sections for Args and Returns, and each sentence adds value without redundancy. It's front-loaded with the core purpose, though it could be slightly more concise by integrating the default note into the Args section more seamlessly.

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 (3 parameters, no annotations, but with an output schema), the description is partially complete. It covers the basic purpose and parameters but lacks behavioral context and usage guidelines. The presence of an output schema mitigates the need to explain return values, but overall, it doesn't provide enough information for confident tool selection and invocation.

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?

The description adds minimal semantics beyond the input schema: it explains that 'namespace' and 'name' identify the provider with examples, and notes the default for 'version'. However, with 0% schema description coverage, it doesn't fully compensate by detailing constraints (e.g., valid namespace formats) or the meaning of 'latest'. The examples are helpful but insufficient for complete parameter understanding.

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 verb ('Get') and resource ('detailed information about a specific Terraform provider'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_provider_docs' or 'get_provider_data_source_docs', which might also retrieve provider information but with different scope or detail.

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 provides no guidance on when to use this tool versus alternatives like 'get_provider_docs' or 'search_providers'. It lacks context about prerequisites, such as whether the provider must be installed or available in a registry, and doesn't mention any exclusions or specific use cases.

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