security_guidelines

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions enterprise-grade security, access control, and audit trails, but does not explicitly state whether actions are read-only or have side effects. The actions listed all appear to be read-only queries, but this is never clarified, leaving room for ambiguity.

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 actions, categories, standards, and features, and ends with a practical example. It is somewhat longer than necessary—particularly the 'SECURITY FEATURES' section, which partly repeats capabilities already stated—but the organization makes it easy to scan and the content is largely non-redundant.

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 complexity (9 parameters, 4 actions, multiple categories and standards), the description covers all major aspects: supported actions, categories, compliance standards, and an example. An output schema exists, so the lack of explicit return-value details is acceptable. The description is complete enough for an agent to select and invoke the tool 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 covers all 9 parameters with descriptions, so the baseline is 3. The description adds value by elaborating on the meaning of 'category' values (e.g., 'best_practices: Security best practices and recommendations') and explaining each compliance standard (SOC2, ISO27001, GDPR, HIPAA), which goes beyond the schema's simple enum lists.

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 opens with a clear statement of purpose: 'Comprehensive security guidance and compliance management', then enumerates four distinct actions (get_guidelines, validate, audit, compliance_check). This clearly distinguishes the tool from siblings that manage secrets or auth methods, as it focuses on guidance, validation, and compliance rather than operational management.

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 lists supported actions and categories, and includes an example ('Perform security audit and compliance check for SOC2 requirements'), which provides clear context for when to use the tool. However, it does not explicitly state when not to use it or mention alternative tools, such as manage_secrets, for related but different tasks.

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