start_session

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool sends no traffic and creates a session, but it does not explain the session's persistence, idempotency, or any authorization or rate limit 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 concise sentence that front-loads the most important information ('FIRST TOOL'). Every word is purposeful, though it could be slightly more structured with bullet points for clarity.

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 has 8 parameters (7 required) and no schema descriptions, the description is insufficient. It does not explain the session lifecycle, how subsequent tools depend on it, or what the output schema contains.

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 0%, so the description must compensate but fails to do so. It only instructs to ask for every field without explaining what each parameter means, e.g., 'allowed_activities' enum values, 'rules', or 'forbidden_tests'.

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 it is the 'FIRST TOOL' that creates an engagement session and sends no traffic. The verb 'create' and resource 'engagement session' are specific, and it distinguishes itself from sibling tools like scan_high_signal or preflight_target.

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 explicitly says 'FIRST TOOL' and instructs to ask the user for every field before invoking, providing clear usage context. However, it does not specify when not to use this tool or list alternative tools for similar purposes.

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