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

With no annotations, the description carries the full burden and does substantial work: it discloses case-insensitivity, per-entity result caps, trade-count ordering, and the important aggregation behavior where multiple spellings collapse into one row with summed trade_count, which can make downstream get_member_trades return fewer trades. It does not mention read-only safety, rate limits, or the exact fields returned, so it falls short of exhaustive.

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 capability is front-loaded in the first sentence, followed by result semantics, then the intended use case, then the known caveat. Every sentence contributes a distinct fact with no filler, despite the description being fairly dense.

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 two-parameter lookup with no annotations and no output schema, the description covers what is matched, how results are capped and ordered, and the key aggregation pitfall. It could add a sentence on the returned fields (e.g., whether ticker and member results are in separate lists) but the essential call-time information is present.

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%, so the schema already documents both parameters and a baseline of 3 applies. The description goes beyond it by clarifying that limit applies independently to members and to tickers (up to limit of each), which changes how an agent sizes the value.

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 set: case-insensitive substring search over member names, ticker symbols, and company names. It also explains its role relative to siblings, positioning itself as the resolver that feeds get_member_trades and get_member_profile, so an agent can distinguish it from the lookup tools without comparing schemas.

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 an explicit routing rule: use this to turn a common or partial name into the exact stored name that get_member_trades and get_member_profile require. It also states a clear boundary condition, that matching is substring-only with no misspelling correction, which tells the agent when this tool will fail and another approach is needed.

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