search_global_section_elements

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

No annotations exist, so the description must carry the safety/behavior burden. It discloses the non-dumping behavior ('without dumping the whole tree') but does not explicitly state that the operation is read-only, describe return format, or mention rate limits. The verb 'Search/filter' implies non-mutating, but richer disclosure would be needed for full transparency.

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?

Two concise sentences front-load the purpose and then list filter options. Every word is useful; no redundant content.

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?

The description defines the tool's purpose, filtering capabilities, and efficiency trait, which is sufficient for a basic filtered-list tool. However, there is no output schema and no mention of result structure or pagination behavior, leaving some ambiguity as to the exact response shape.

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?

The schema covers all 9 parameters with descriptions, so the baseline is 3. The description lists the filter types but largely restates parameter names from the schema without adding new syntax or format details beyond what is already structured.

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 uses a specific verb 'Search/filter' and names the resource 'elements within a global section (Header/Footer/block)', immediately distinguishing it from a full tree dump. It also enumerates filter dimensions, making the scope clear relative to sibling tools like search_page_elements or search_global_source_elements.

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?

It states the benefit 'without dumping the whole tree', implying this tool is for targeted queries when a filtered subset is needed. It does not explicitly name alternatives or exclusions, but the context makes the intended use clear.

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