find_ue_macros

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

With no annotations, the description must disclose behavioral traits. It indicates a read-only search operation, but lacks details on authentication needs, rate limits, or whether the search is real-time or index-based. It adds minimal value beyond what the name and schema imply.

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, well-frontloaded sentence that conveys the core purpose and filtering capability without any extraneous words. Every part earns its place.

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?

While the description covers the basic purpose and aligns with the schema, it does not explain output expectations, pagination, or default values (e.g., max_results=50). Given no output schema and moderate complexity (4 parameters), the description is minimally adequate but could provide more context.

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 schema already documents all parameters. The description mentions 'optional filtering by type and specifiers', which reinforces the schema but does not add new semantic meaning, meeting the baseline of 3.

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 searches for UE macros, lists specific types (UCLASS, UPROPERTY, etc.), and mentions optional filtering, which distinguishes it from generic search tools like find_references or search_symbols.

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 implies the tool is used to find UE macros with filters, but it does not provide explicit guidance on when to use this tool versus sibling tools like find_callers or get_macro_specifiers, nor does it mention exclusions or prerequisites.

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