timps_phishing_simulator

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

With no annotations provided, the description carries the full burden of behavior disclosure. It does not state whether emails are actually sent, whether target lists are required, how payloads are tracked, or what safety mechanisms exist beyond the ethical note. This is especially concerning for a security-sensitive tool.

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 concise sentence plus an ethical clause, front-loading the core purpose and key deliverables. It avoids fluff, though a slightly more structured breakdown could improve readability.

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 security-sensitive and has no output schema, so the description should explain return values, required contextual inputs, and safety boundaries in more depth. It lists deliverables but omits whether anything is sent, how results are presented, and what happens after generation.

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% for both 'request' and 'language', so the schema already documents the parameters clearly. The tool description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 'Generate' and clearly identifies the resource as an 'organisation-tailored phishing simulation' with concrete deliverables (emails, landing pages, payload tracking, click-through metrics). It is distinct from sibling security tools like timps_red_team_agent but does not explicitly name alternatives, so it misses the top score.

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 phrase 'Strictly for authorised training use' provides an explicit boundary for when the tool should not be used. The opening 'Generate a realistic phishing simulation' implies the primary use case. However, it does not mention alternative tools or further when-to-use guidance, keeping it from a 5.

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