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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds non-obvious data-disclosure behavior beyond that — short books are aliased and open M&A baskets are withheld — plus 'no auth'. That redaction semantics is exactly the kind of context an agent cannot infer from structured fields.

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?

Front-loaded with the core claim ('One fund in full public detail'), then a dense but well-ordered field inventory, ending with the read-only/auth note. Every clause carries information, though the mid-sentence parentheticals make it slightly heavy for a single-parameter read.

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 must carry the return contract — and it does, enumerating the fields returned and flagging the two cases where constituents are withheld or aliased. With annotations covering the safety profile, nothing material is missing for a correct invocation.

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 coverage is 100% for the single symbol parameter, so the baseline is 3. The description adds value above that by naming the source of valid values (list_funds) and giving concrete examples of symbol formats (AIB symbols, MA-RIPPLE, FTA-CRYPTOS, FTA-STOCKS, EVENT-CARD), which helps the agent construct a valid call.

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?

States a specific verb ('Get') and resource ('one fund') and immediately enumerates the scope of the payload: theme, mandate, direction, status, constituents, price, return, URLs, focus areas. This clearly separates it from siblings like list_funds (enumeration) and get_fund_history (time series).

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?

Gives the required precondition for the input ('Symbol from list_funds') and even lists valid symbol families, which tells the agent where to source the argument. It does not explicitly say when to prefer this over get_fund_history or get_fund_methodology, so it stops short of full alternative routing.

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