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

The readOnlyHint annotation already covers safety, and the description adds meaningful behavioral context by specifying the type of information returned: persistent advantages, weaknesses, open risks, confirmed patterns, and business context. It does not discuss output format or staleness, but for a read-only getter this is reasonably transparent.

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 compact sentence with a colon-separated list, front-loading the core concept and avoiding filler. Every phrase contributes meaning.

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 simple two-parameter schema, the read-only annotation, and the absence of an output schema, the description provides enough contextual coverage: it names the kind of content an agent will receive. It could be more complete with an explicit output shape or an example, but the tool is simple enough that this is a minor gap.

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 description indirectly gives meaning to perCategoryLimit by listing the categories it applies to, and the schema already documents its default. However, the required symbol parameter has no schema description and the description does not clarify it beyond the tool name, so the parameter semantics are only partially compensated.

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 conveys that this tool provides a company's decision-focused memory: durable strengths, weaknesses, open risks, confirmed patterns, and business context. It implies the resource and content, though it lacks an explicit verb such as 'returns' or 'retrieves' and does not distinguish itself from sibling tools like get_company_analysis.

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?

Usage is implied rather than explicit: an agent would use this when it needs persistent, qualitative company context rather than real-time signals. However, the description names no alternatives and gives no when-not-to-use guidance, leaving sibling differentiation to inference.

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