endpoint_search

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

The description discloses paging behavior (size <= 500, from <= 10000) and mentions sort for deeper paging. However, it makes a claim that q, from, size are required, contradicting the schema where all parameters are optional (nullable). No information about authorization, rate limits, or side effects is provided, and annotations are absent.

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 very concise, consisting of just two sentences that convey the core functionality, filter format, and paging constraints. Every sentence adds essential information without redundancy.

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 description covers the main filtering and paging aspects but lacks details on other parameters (group, includeFields, body) and the response structure. Since there is no output schema, more context about return values would be beneficial for complete understanding.

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 description adds significant value beyond the schema by explaining the RSQL filter syntax with an example and specifying constraints on size and from. It also hints at using sort and seek paging, which aids understanding of the 'sort' parameter even though schema coverage is 100%.

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 it is for searching endpoints/assets, provides an example RSQL query, and mentions paging limits. However, it does not differentiate from sibling tools like endpoint_attributes_search, which also search endpoints but on different attributes.

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 description explicitly states 'Required: q, from, size' and advises using sort + seek paging beyond 10000, giving some usage guidance. However, it does not explain when to use this tool over alternatives or when not to use it.

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