search_global_source_elements

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only the assertion that no component parameter is required, which is mildly useful context, but says nothing about result limits (the 50 default), pagination, or the shape of the returned element set for a tool with 10 parameters.

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 purpose sentence is front-loaded and the examples are scannable. The bullet list is slightly redundant with the schema descriptions, but each bullet maps a filter to a concrete use case rather than padding.

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?

For a 10-parameter read tool with no output schema, the description covers filter usage adequately but omits the default result cap, pagination behavior, and any routing against the many neighboring element-search tools. Adequate but with clear gaps.

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 description coverage is 100%, so the baseline is 3. The examples add concrete sample values for the filter parameters (type="button", custom_class="hero", text="subscribe"), which is modest added value, but the semantics of each flag are already fully stated in the schema.

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?

States a specific verb and resource: search/filter elements within a global source. It is distinguishable from the similarly named search_global_section_elements and get_global_source_element by the 'within a global source' scope, though it never names those siblings explicitly. The odd 'No component param needed' line slightly muddies the scope since the schema does expose a component parameter.

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 six examples effectively demonstrate when each filter is useful (buttons, classes, text, bindings, events), which is better than nothing. However, there is no statement of when NOT to use this tool or which sibling to prefer for a single-element lookup or section-scoped search, leaving the routing decision to inference.

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