Returns AgentAegis FAQ — authentication, balance/billing, tool catalog, async jobs, error codes, x402, rate limits, security. Optional topic filter. Free to call.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds 'Free to call' and explains the optional filter, providing useful context without contradicting 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?
A single, front-loaded sentence that conveys purpose, scope, and optionality with no wasted words.
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 is simple with one optional parameter, no output schema, and clear annotations. The description provides sufficient context for an agent to understand and invoke it correctly.
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 one parameter with an enum, but no descriptions. The description compensates by explaining the topic filter and listing several example topics, though it does not enumerate all possible values or add detailed semantics for each.
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 returns an FAQ and lists the main topics covered. It uses a specific verb ('Returns') and resource ('AgentAegis FAQ'), distinguishing it from sibling security tools.
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 use for general informational queries with an optional topic filter and notes it is free to call, but does not explicitly state when to use it versus alternatives or list exclusions. Context makes it clear it is the go-to help resource.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes with detailed descriptions that disambiguate overlaps (e.g., dns_security_check vs email_security_audit, ssl_tls_audit vs vet_endpoint). A few compliance lifecycle tools (compliance_framework_check, control_gap_analysis, audit_report_generate) could be confused, but descriptions clarify their sequencing.
All tool names use lowercase snake_case, but the verb/noun order varies (e.g., access_review vs agent_history vs cve_lookup). The pattern is readable and predictable enough, with minor inconsistency in whether the resource or action comes first.
28 tools is on the heavy side, exceeding the 25-tool threshold for 'too many' in the calibration. However, the broad security/compliance domain justifies the count, and each tool covers a distinct aspect, though some consolidation (e.g., email_security_audit vs dns_security_check) could reduce redundancy.
The toolset covers the full security assessment lifecycle: identity/access review, vulnerability discovery and prioritization, compliance frameworks and gap analysis, evidence collection, policy generation, incident triage, and specialized scans (code, secrets, network, web app, MCP/skill supply chain). No obvious critical gaps for the stated purpose.