search_recordings_metadata

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

With no annotations, the description should disclose behavioral traits. It implies a read operation ('search'), but does not explicitly state it is read-only, nor does it mention rate limits, authentication, or side effects. The tool name suggests metadata is returned, but the description says 'search recordings', which is slightly ambiguous.

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 sentence, which is concise. However, it lacks structure such as bullet points or separate sections. For a tool with three parameters, it is acceptably brief but could include more detail without being overly verbose.

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?

Given the tool has three parameters (including a nested object), no output schema, and no annotations, the description is incomplete. It does not explain pagination, result format, or whether it returns metadata or full recordings. The context of sibling search tools suggests more specificity is needed.

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 0%, meaning the schema lacks property descriptions. The description mentions date range, which correlates with the date_range parameter, but does not explain limit and offset for pagination. It adds minimal meaning beyond the raw schema.

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 'search' and the resource 'recordings' with a specific filter 'by date range'. However, it does not distinguish this tool from sibling search tools like search_by_confidence or search_by_validation_status, so it lacks full differentiation.

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 provided on when to use this tool versus alternatives. Given the many sibling search tools, the description should indicate that this tool is for date-range-based searches and that other tools are for other criteria. There is no such guidance.

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