organization_publisher_operating_systems_search

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

Lacks annotations, so description must carry full burden. It mentions 'Returns events' but does not clarify side effects, safety, or whether it is read-only. Additionally, it claims parameters q, from, size are required, contradicting the input schema where they are optional.

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 a single sentence, but it redundantly includes the tool name and API path. It is concise but lacks effective structure and fails to prioritize key information.

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 7 parameters, no output schema, and many sibling tools, the description is highly incomplete. It omits return format, pagination details, filtering semantics, and how it differs from similar 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%, but descriptions are minimal (e.g., 'query param q (str)'). The tool description adds no extra meaning beyond listing required parameters (incorrectly). Baseline 3 is appropriate.

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 'Returns events' but does not specify what kind of events or the role of operating systems. It is minimal and only slightly better than a tautology.

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 siblings like organization_endpoint_publisher_operating_systems_search or other search tools. The description provides no context for selection.

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