pulsedive_search

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the return shape ('matching indicator IDs') which is genuinely useful given no output schema, but it says nothing about rate limits, auth, or token requirements expected of an open-world search API.

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?

Two tight sentences with zero filler, and the core purpose is front-loaded. It is efficient, though the extreme brevity leaves no room for routing or format hints.

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 single-parameter read tool with annotations covering safety and no output schema, the description covers purpose and return shape. It omits the two things most needed here: how to phrase the query value and when to prefer the sibling Pulsedive tools.

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% and the single 'query' parameter is documented in the schema, so the baseline is 3. The description's 'by value' adds a little meaning (searching on the indicator value itself) but no syntax, format, or example beyond what the schema provides.

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?

States a specific verb and resource ('Search Pulsedive indicators by value') and clarifies the query operates on indicator values. It does not differentiate from the sibling tools pulsedive_indicator and pulsedive_explore, so an agent can't tell from the description alone which Pulsedive lookup to pick.

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 when-to-use guidance and no mention of the sibling alternatives (pulsedive_indicator for known indicators, pulsedive_explore for pivoting). 'By value' hints at the query form but no conditions or exclusions are given.

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