search_by_notify

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the purposeful operation ('Find animations') without mentioning read-only nature, output format, permissions, or side effects. Minimal additional context beyond the obvious.

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 extremely concise: a one-line purpose followed by a clear Args list. Every sentence earns its place, with no redundancy or fluff.

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 simple search tool with an output schema present, the description provides sufficient context to select and invoke the tool. It covers the purpose and parameters, though it lacks explicit edge-case handling or alternative guidance. Adequate for the task.

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 Args section provides concise explanations for all three parameters, which is essential because the schema lacks property descriptions (0% coverage). Descriptions clarify the role of notify_name, notify_class, and folder, though they are minimal and could be more specific (e.g., folder path syntax).

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 verb 'Find' and the resource 'animations', with a specific search criterion 'specific notify'. It distinguishes from sibling search tools like search_by_curve and search_by_slot by focusing on notifies.

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?

Usage is implied: use this when you need to locate animations by notify name/class or restrict to a folder. However, no explicit alternatives or exclusions are given, leaving the agent to infer differentiation from sibling tools.

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