shodan_facets

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the context that facets relate to 'search result breakdowns,' which is useful. Yet it does not disclose return format, API key requirements, or rate limits. Thus moderate additional value beyond 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 a single, front-loaded sentence containing only essential information. It avoids redundancy and is immediately actionable.

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, parameterless metadata-listing tool, the description is adequate. It states what the tool returns (a list of facets) and its purpose. However, without an output schema, it could optionally elaborate on the nature of the facets, but this is not necessary for a tool this simple.

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 tool has zero parameters, so the description need not explain parameter syntax. The baseline of 4 applies because there is no parameter semantics burden; the description correctly makes no parameter-related claims.

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 uses a specific verb and resource: 'List all facets available for search result breakdowns.' It clearly states the tool's action (list) and scope (facets for search breakdowns), distinguishing it from sibling tools focused on search, host, DNS, scans, alerts, and CVEs.

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 purpose implies usage: call this to retrieve facet options before doing search result breakdowns. However, it does not explicitly contrast with alternatives like shodan_filters or mention when not to use it. Usage context is implied but not stated directly.

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