endpoint_attributes_search

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

The description only says 'Returns events' with no details on pagination, authentication, or side effects. It also inaccurately marks q, from, size as required (schema shows optional), which could mislead. No annotations to compensate.

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 short (one sentence) and front-loaded with endpoint, but it lacks essential information. It is not appropriately sized for the tool's complexity.

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?

With no output schema, no annotations, and 7 parameters, the description is grossly incomplete. It does not explain return format, filtering behavior, or the purpose of parameters like group, sort, body, includeFields.

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 covers all 7 parameters with descriptions, so baseline is 3. However, the description incorrectly states that q, from, size are required, while schema shows optional. This adds confusion and reduces value.

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 states the tool returns events and gives the endpoint URL. However, 'events' is vague and does not differentiate from sibling search tools for other entities. The meaning is partially clear but lacks specificity.

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 like endpoint_search or automation_search. No prerequisites or context for usage are provided.

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