Close Session

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

The annotation destructiveHint=true already indicates destructive behavior. The description adds 'clean up resources,' providing context about side effects, but it does not detail what happens to the session (e.g., whether it logs out, closes browser, or releases credentials). With annotations covering the destructive nature, this is adequate but not overly 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 is front-loaded with the action ('Close') and resource ('Instagram browser session'). Every word earns its place; no fluff or redundancy.

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's simplicity (no parameters) and the presence of an output schema, the description sufficiently communicates the action. Minor gap: it doesn't state whether the session is invalidated or just closed, but for a close-session tool this is acceptable. Overall, complete enough.

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 the description carries no burden of explaining parameter meanings. The schema is trivially complete, and the description adds value by clarifying the action's purpose. Baseline for 0 params is 4.

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 ('close') and resource ('current Instagram browser session'), clearly distinguishing this from sibling tools which focus on data retrieval or social actions. It also indicates cleanup of resources, which adds scope clarity.

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 implies usage by mentioning 'current session,' but it does not explicitly state when to use this tool versus alternatives (e.g., 'use when you are done with a session'). Since there are no alternative session tools among siblings, the guidance is somewhat implicit rather than explicit.

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