session_find_address

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

With no annotations, the description provides meaningful behavioral context: searches across all tool outputs and returns sessions. It does not disclose exact matching semantics or return format, but for a search tool this is adequate and adds value beyond the schema.

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, well-structured sentence that is immediately clear and free of unnecessary information. It is appropriately sized for the tool's simple operation.

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 one-parameter search tool, the description effectively communicates what the tool does and what it searches. The lack of an output schema is mitigated by the implied result (all matching sessions). Minor gap: no mention of return format or search semantics, but overall adequate.

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 input schema fully describes the single parameter, including an example format. The description repeats no parameter details, so with 100% schema coverage, the baseline of 3 is appropriate.

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 is highly specific with a clear verb ('Find') and resource ('sessions'), stating the exact filter (hex address in any tool output). It clearly distinguishes from sibling tools like session_find_function by focusing on hex addresses.

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 clearly implies the use case: searching sessions for a hex address. It does not explicitly mention alternatives or exclusions, but the context is sufficiently clear given the tool name and its focus on addresses.

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