sc_search

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states a scope and gives no information about search semantics, authentication, rate limits, result format, pagination, or side effects. The word 'Search' implies a safe read, but that is not made explicit.

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 concise sentence with no filler or repetition. It is appropriately short for a simple tool, though the brevity comes at the cost of missing useful behavioral and parameter detail.

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 that the tool has only two parameters and an output schema, the description is not overly complex to write, yet it leaves key context unexplained. An agent would not know what kind of security identifiers to pass, how portfolio_id modifies the search, or what type of results to expect beyond what the output schema might provide.

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%, and the description mentions neither 'query' nor 'portfolio_id'. It does not explain what 'query' should contain, whether it matches ticker names, company names, or other identifiers, or what effect the optional portfolio_id has on the search.

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 a specific verb and resource: 'Search securities' within the 'Scalable Capital broker portfolio context.' This clearly conveys the core action, though it does not explicitly differentiate the tool from siblings like sc_quote or sc_holdings.

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?

The phrase 'within the Scalable Capital broker portfolio context' implies a scoped search use case, but no explicit guidance is given about when to use this tool versus alternatives such as sc_quote or sc_holdings. There are no stated exclusions or conditions that would help an agent choose between siblings.

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