search_global_source_elements

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

With no annotations, the description carries the full burden. It adds the key behavioral note 'No component param needed' and gives filter examples, but lacks disclosure of return format, pagination, limit behavior, or error handling. It is not misleading, but it does not provide rich behavioral context beyond the schema.

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 succinct and front-loaded with the core purpose. Examples are presented as a bulleted list, making it scannable. Every sentence contributes to understanding the tool's usage, with no filler.

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?

Given the 10 parameters and no output schema, the description handles complexity well by providing illustrative examples for common use cases. It does not explicitly explain the return value or default limit, but the tool's purpose is clear and the schema covers the limit. Minor gaps prevent a 5.

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%, so the baseline is 3. The description adds value by showing concrete usage examples for multiple parameters (type, custom_class, text, has_bind, has_events, has_custom_class), clarifying how to combine filters effectively. This goes beyond what the schema provides.

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's function: 'Search/filter elements within a global source.' It further differentiates from siblings like search_page_elements by noting 'No component param needed,' making the scope explicit. Examples reinforce the specific resource and operation.

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 provides clear context for when to use the tool and includes practical examples for filtering by type, class, text, and flags. It hints at an alternative (component-based search) with 'No component param needed' but does not explicitly name alternatives or exclusion conditions, which keeps it slightly below a 5.

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