organization_endpoint_group_search

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

No annotations are provided, and the description only says 'Returns events' without detailing side effects, authentication needs, or rate limits. The POST method implies potential mutation but this is not clarified.

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, but it lacks clarity and includes incorrect information. Conciseness alone is insufficient without accuracy.

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 and no annotations, the description fails to explain pagination, response structure, or the distinction from many sibling search tools. The tool appears to be a search but 'events' is undefined.

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 descriptions are generic (e.g., 'query param q (str)') and the description adds no meaningful context. It misstates requiredness, contradicting the schema where all parameters have default null. Baseline 3 for 100% coverage is reduced due to misleading information.

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 says 'Returns events' but the tool name indicates searching for endpoint groups, creating ambiguity. It also incorrectly lists q, from, size as required when schema shows they are optional.

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 sibling tools like 'organization_endpoint_group_search_by_fields' or 'endpoint_search'. The description does not specify use cases or exclusions.

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