pulsedive_search

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic functionality and output type. It does not mention whether the tool is read-only, if any authentication or rate limits apply, or the scope of the search. This is insufficient for an agent to understand the tool's operational behavior.

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 extremely concise at two sentences, with no unnecessary words. It directly states the action and result. Fits the principle of front-loading essential information.

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 simplicity (one parameter, no output schema), the description covers the basic purpose and return type. However, for complete context, an agent might need more details about the search scope, data coverage, or expected response structure. It meets minimal viability but leaves gaps.

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% but the schema description for 'query' is generic ('Search query'). The tool description adds value by specifying that query is an 'indicator value' (by value), which clarifies the parameter's semantics. However, no further detail is given about acceptable value formats or constraints.

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?

Description clearly states the tool searches Pulsedive indicators by value and returns matching indicator IDs. The verb 'Search' and resource 'indicators' are specific, and the return type is mentioned. Distinguishes from sibling tools like pulsedive_explore and pulsedive_indicator which have different purposes.

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 versus alternatives, such as pulsedive_indicator (for individual indicator details) or pulsedive_explore. No mention of query format, limitations, or prerequisite knowledge. The description is too minimal to provide effective usage context.

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