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

Annotations already declare the tool is read-only, idempotent, non-destructive, and closed-world, and the description adds substantial behavior beyond that. It explains resolved=false, ambiguous matches, gated Premium entitlement, the specific absence signal, subject identifier echoing, current-projection versus historical-version semantics, and open verdict behavior.

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 long, but it is front-loaded with purpose and usage, then organized around distinct edge-case rules. Most sentences carry unique behavioral information, though some return-state detail may overlap with the output schema.

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 read-only annotations and the presence of an output schema, the description is largely complete for correct invocation and interpretation. It explicitly covers ambiguous, gated, and absent-record states, but leaves exchange parameter semantics under-specified.

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 only 33%, so the description must compensate. It does clarify that identification can be by ISIN or by ticker with an optional exchange, but it does not explain exchange value semantics, precedence when both ISIN and ticker are supplied, or how ticker and exchange interact for matching.

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 states a specific verb and resource: read the investor's own recorded investment thesis for one instrument. It also specifies the identifying modes (ISIN or ticker with optional exchange) and the substantive content returned (statement, falsifier, dates, conviction, verdict), which clearly separates it from siblings such as get_journal or get_reflection_history.

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?

It gives clear usage context: recalling the investor's premise before discussing their own recorded instrument, or when the investor asks what they thought. It does not name alternatives or explicitly state when not to use this tool, so it falls short of full routing guidance.

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