search_quantconnect

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description does not add any behavioral context beyond that, such as which content sources are searched or if there are rate limits. The schema does provide type options (Stubs, Forum, Docs, Examples), but the description omits this.

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, clear sentence. It is concise and to the point, but could benefit from a little more structure or detail about the search scope.

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's complexity (search across multiple content types with language and criteria arrays) and the presence of an output schema, the description is too minimal. It does not explain the output format, supported types, or how to construct a valid request beyond what the schema provides.

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?

The input schema has only one top-level parameter (model) with no description, but the nested properties (input, type, count, language) have descriptions and examples. The tool description does not add any additional meaning beyond what the schema provides, so a baseline 3 is appropriate.

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 'Search for content in QuantConnect' clearly states the action (search) and resource (QuantConnect content). It distinguishes from siblings because no other tool is named as a search tool, and the title from annotations reinforces the purpose.

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?

No guidance on when to use this tool over alternatives. There is no mention of limitations, prerequisites, or when not to use it. The agent has to infer based on the name alone.

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