search_modules

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

With no annotations provided, the description carries full behavioral burden. It discloses the search prefix, optional query filtering, and the exact return fields. It doesn't mention authentication, rate limits, or pagination, but it's a read-only search operation and the behavior is reasonably transparent.

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: a one-sentence purpose, a clarification of filtering, and explicit Args/Returns sections. Every sentence serves a purpose, and it's appropriately brief for a simple tool.

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?

The tool has one optional parameter, an output schema, and clear context. The description explains the prefix, query behavior, and return fields, making it complete for an agent to understand what the tool does and what it returns.

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 schema has no description for the 'query' parameter and coverage is 0%. The description explicitly explains the parameter as an optional filter to narrow results by service name, fully compensating for the schema's lack of detail.

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 that the tool searches for Terraform modules in a GitHub organization, listing repositories with the prefix 'terraform-aws-module-'. This specific verb+resource combination (search/list modules) distinguishes it from siblings like get_module or list_module_versions.

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 explains the default behavior (list all matching prefix) and how an optional query filters by service name. It implies its role as the discovery tool among siblings, though it does not explicitly mention when not to use it or direct users to an alternative.

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