find_documents

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

Given the lack of annotations, the description carries the full burden. It indicates a read-only retrieval operation but does not disclose return format, pagination, or side effects. The existence of an output schema partially mitigates this, but more detail would be beneficial.

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, efficient sentence with no unnecessary words. It front-loads the core action and resource.

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 retrieval tool with an output schema, the description provides a high-level purpose but lacks parameter explanations and usage context. It is minimally adequate but leaves gaps about how the tool behaves with different inputs.

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%, so the description must compensate. It adds context about the type of documents (educational) and videos (complementary) but fails to explain the purpose of parameters like 'query', 'video_limit', and 'document_limit'. The description does not clarify how these are used together.

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 'retrieve' and the specific resource 'educational documents enriched with complementary videos', distinguishing it from sibling tools like search_youtube (which focuses on videos) and health_check (a monitoring tool).

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 provides no guidance on when to use this tool versus alternatives like search_youtube or run_workflow, nor does it specify any prerequisites or exclusions.

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