search_by_date_range

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

With no annotations, the description carries the full burden, but it says 'created within a date range' while the schema supports date_created, date_modified, and date_imported via date_field. This is misleading. It also does not describe pagination behavior, inclusive date boundaries, or that query can further narrow results.

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 front-loaded sentence with no filler or repeated information. The wording is tightly compact, though the omission of key scope details prevents a higher score.

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 six-parameter tool with no annotations and no output schema, this description is too sparse. It ignores optional search/pagination parameters, the date_field selection, and the relationship to sibling search tools, so an agent would need to inspect the schema closely and still may mis-invoke it.

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 67%, so the description needs to add value, but it only contributes 'created' and 'date range'. It does not explain query, page, per_page, or the configurable date_field, and its 'created' wording actually conflicts with the date_modified and date_imported enum options.

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 states a clear verb (Search), resource (assets), and scope (created within a date range), so an agent understands the core action. It does not explicitly distinguish this from sibling search tools like search_assets, search_by_metadata, or search_faceted, and its use of 'created' is narrower than the actual date_field options.

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?

No guidance is given about when to choose this tool over the many sibling search tools. The description implies date-range asset searching but does not mention alternatives, exclusions, or scenarios where this tool is preferred.

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