sc_search

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention idempotency, rate limits, authentication requirements, or what happens if the query yields no results. The description only states the scope but omits key behavioral context.

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 sentence with moderate conciseness, but it lacks structure or front-loaded key details. It earns its place minimally but could be more efficient by stating scope upfront.

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 tool has an output schema (making return values documented) but 0% schema description coverage and no annotations, the description fails to provide usage context, query format, or filtering behavior. The portfolio context is hinted, but the description is insufficient for correct tool selection and 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 description coverage is 0%, meaning neither description nor schema explains what 'query' means (e.g., ISIN, name, ticker) or how 'portfolio_id' filters results. The description adds no parameter-level details. Baseline for low coverage is below 3, and this fails to compensate.

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 'Search securities within the Scalable Capital broker portfolio context,' which gives a verb (search) and resource (securities) with scope (portfolio context). However, it does not differentiate from sibling tools like sc_security_news or sc_quote that also involve securities. The purpose is adequate but vague.

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?

There is no guidance on when to use this tool over alternatives such as sc_holdings, sc_transactions, or sc_security_news. The description implies usage in a portfolio context but does not exclude cases like searching outside a portfolio or clarify required prerequisites. No explicit when/not guidance.

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