boond_timereports_search

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

No annotations are provided, so the description carries the full behavioral burden. It only restates the search capability and filter dimensions but does not disclose default behavior around pagination, how filters interact, response format, permission requirements, or any edge cases.

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 that wastes no words and communicates the core search capability and the main filter dimensions immediately. It is appropriately sized for a simple search tool.

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 tool with six optional parameters, no output schema, no annotations, and no parameter descriptions, the description is too thin. An agent has no guidance on pagination defaults, valid filter combinations, response shape, or any constraints beyond what the schema property names already expose.

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?

With 0% schema description coverage, the description must compensate for the six parameters. It maps three groups (resource, date range, status) to resourceId, startDate/endDate, and status, but it leaves page and limit semantically unexplained and provides no details about date formats or filter matching behavior.

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 the verb 'Search', the resource 'time reports', and the three filter dimensions (resource, date range, status). This clearly identifies what the tool does and distinguishes it from timereports_get or timereports_create at a basic level, though it does not explicitly name or differentiate against sibling tools.

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 phrasing 'Search time reports by resource, date range, or status' implies when to use this tool, but it offers no explicit guidance about when to prefer it over boond_timereports_get or other search tools, and it does not state any exclusions or preferred alternatives.

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