Search Cymulate Findings

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds that filters go in the request body, which is a useful behavioral note beyond annotations. However, it does not discuss pagination behavior, response format, or potential limitations.

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 concise sentences, front-loaded with the main purpose. Every word contributes: 'search findings', 'across the platform', 'with filters', and the note about request body. No fluff or repetition.

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?

The tool has no output schema, so the description should explain what the search returns, but it does not. It also omits any mention of pagination, even though the schema defines it. For a search tool with nested objects and multiple sibling tools, this description is incomplete.

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 50%: 'filters' has only 'Filter body', pagination has no description. The tool description adds examples of filter keys (severity, module, MITRE tag, date range) which helps understand the filters parameter. However, it does not explain pagination semantics, leaving that gap partially filled by schema constraints (page/limit min/max).

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 clearly states the tool searches findings across the platform with filters, providing a specific verb ('search') and resource ('findings'). It distinguishes from siblings like cymulate_findings_get_filters (which likely returns filter options) and cymulate_findings_get_info, though it does not explicitly compare to similar 'get_findings' tools.

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. The description mentions filters go in the request body, but does not specify use cases, prerequisites, or when not to use it. There is no mention of alternatives.

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