Workflow: Security Posture

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

Annotations already establish that this is a safe, read-only, non-destructive, closed-world operation. The description adds important behavioral context by clarifying that it returns step-by-step instructions rather than performing the briefing or pentest itself, and that the scope is the 5 most recent pentests. It does not detail the instruction format or whether fewer than five pentests changes the output, but the key behavior is disclosed.

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 with no wasted language. It front-loads the primary purpose and then provides the client-compatibility condition.

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 zero-parameter workflow-instruction tool with no output schema, the description is nearly complete: it states what is returned, the scope of pentests, and the client condition. A minor gap is that it does not describe the structure or limitations of the returned instructions, but the essential information for correct invocation is present.

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 there is no parameter semantics for the description to compensate for. The baseline for a zero-parameter tool is 4, and the description does not need to explain parameters.

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: it returns step-by-step instructions for producing an executive security posture briefing across the 5 most recent pentests. This clearly distinguishes the tool from data-fetching and pentest-execution siblings by emphasizing that it generates guidance rather than running analysis itself.

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?

It explicitly says to use this in MCP clients that don't support the 'security_posture' MCP prompt directly, which gives a clear usage condition and implies the prompt is the alternative when supported. It does not explicitly state when not to use the tool or mention sibling workflow tools as alternatives, but the context is clear.

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