FOFA Search Stats

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only mentions a rate limit (throttling) but does not state if the tool is read-only, idempotent, or requires specific authentication. Significant gaps remain.

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 two concise sentences: first states the purpose, second provides critical usage info (throttling) and supported fields. Front-loaded with essential information, no redundancy.

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 that an output schema exists (context indicates true), the description need not detail return values. However, it could better explain that the tool provides aggregated statistics or counts per field. The listed fields are helpful, but the aggregation nature is only hinted at.

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 description coverage is 100%, so baseline is 3. The description adds value by listing the full set of supported aggregation fields (protocol, domain, port, etc.), which goes beyond the schema's default value and clarifies what fields are valid.

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 tool aggregates FOFA search results using the /api/v1/search/stats endpoint, with a specific verb and resource. It also lists supported fields, distinguishing it from sibling search tools that return raw results or paginate.

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 mentions throttling but does not explicitly state when to use this tool versus alternatives like fofa_search or other aggregation tools. Usage context is implied through the term 'aggregate' but no direct guidance is given.

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