tor_delete_session

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds the context that a session credential file is deleted. However, it does not disclose any additional behavioral traits such as whether deletion is permanent, requires confirmation, or fails if the session doesn't exist. With annotations present, this minimal addition is acceptable but not rich.

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 action and object. Every word earns its place, and there is no redundant information.

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 simple deletion tool with annotations and an output schema, the description is minimal but functional. It lacks guidance on necessary prerequisites (e.g., the session must exist) or consequences (e.g., irreversible deletion). It could benefit from mentioning related tools for session management, but overall it provides the core context.

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 has one required parameter 'name' with no description (0% coverage). The description implies that 'name' refers to a saved session file, but it does not explicitly define the parameter's format, accepted values, or relationship to list_sessions. The compensation is minimal.

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 the action (delete) and specific resource (saved session credential file), distinguishing it from sibling tools like tor_save_session, tor_load_session, and tor_list_sessions. The verb+object structure is specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention related tools (e.g., tor_list_sessions for finding session names) or any prerequisites/exclusions. Users must infer usage from the tool name alone.

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