security.test_csrf

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'advanced techniques' but doesn't specify what these entail operationally (e.g., whether it performs actual attacks, requires authentication, has rate limits, or returns structured findings). The description lacks critical behavioral details needed for a security testing tool with potential destructive implications.

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, efficient sentence with no wasted words. It's appropriately front-loaded with the core purpose. However, it could be more structured by separating purpose from technique details, but this is minor given the brevity.

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 security testing tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like safety (could this trigger actual CSRF attacks?), output format, error handling, or integration with sibling tools (e.g., 'db.save_finding'). The context signals indicate significant complexity that the description doesn't adequately cover.

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 75% (3 of 4 parameters have descriptions), so the baseline is 3. The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain how 'testTechniques' relate to 'advanced techniques', provide examples for 'params', or clarify URL format expectations. The description fails to compensate for the 25% coverage gap in the schema.

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 'Test for CSRF vulnerabilities using advanced techniques' states the general purpose (testing CSRF vulnerabilities) but lacks specificity about what resources are targeted or what 'advanced techniques' entail. It distinguishes from some siblings like 'security.test_xss' by focusing on CSRF, but doesn't clearly differentiate from other security testing tools in terms of scope or methodology.

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?

No guidance is provided on when to use this tool versus alternatives like 'security.test_auth_bypass' or 'security.test_xss'. The description doesn't mention prerequisites, target contexts (e.g., authenticated endpoints), or comparison with sibling tools. Usage is implied only by the tool name and general security testing context.

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