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

Annotations already establish that this is a safe, closed-world read, so the description's job is to add richness — and it does, by previewing the return payload in detail and flagging that the named instruments are not selected or endorsed by FinChiefs, which is a meaningful caveat for interpretation. It does not say what happens for an unknown slug or how large the payload can get.

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?

A single front-loaded sentence: the verb-plus-resource comes first, followed by a scannable inventory of what is returned and a closing pointer to the slug source. Dense but no filler.

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?

There is no output schema, so the description carries the burden of describing return contents, and it does so thoroughly, while annotations cover the safety profile. The only gap is failure behavior for a missing or invalid slug, which an agent would otherwise have to discover at call time.

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?

With 100% schema coverage the schema already defines the single slug parameter and gives an example, so the baseline is 3. The description adds real value beyond that by specifying the provenance and authoritative source for slug values, reducing the chance of a hallucinated identifier.

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 opens with a specific verb and resource ("One Investment Theme by slug") and then enumerates exactly what the response contains: thesis, tally, horizons, flags, house stances with notes and source links, named instruments, positioning and related themes. It is clearly distinguishable from the list-level sibling get_investment_themes, which it references as the source of slugs.

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 tells the agent how to obtain the required input ("Slugs come from get_investment_themes"), which is the practical precondition for calling this tool. It stops short of explicit when-not-to-use guidance against siblings like search_asset_views or search_research, but the "full detail for one theme" framing makes the choice reasonably clear.

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