원문 전문 검색

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

No annotations provided, so description carries full burden. It discloses that the tool searches over 1053 PDFs (~22k chunks) and that the first call takes 1-2 seconds. However, it does not describe result ranking, pagination, or rate limits.

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?

Three concise sentences: purpose/scope, usage guidance, and fallback/performance note. No redundant information; every sentence adds value.

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 search tool with 5 parameters, no output schema, and no annotations, the description covers purpose, usage, a behavioral note, and sibling connection. Lacks output format or pagination details, but 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?

Schema description coverage is 100%, so baseline is 3. The description adds context that the query is for full-text content and mentions excerpt truncation, but does not elaborate on each parameter beyond schema. Acceptable but not exceptional.

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 tool searches full text of 1053 PDFs (environmental education materials) with specific examples of use cases. It distinguishes itself from the sibling tool search_resources (metadata search) and get_document_text (full context reading).

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?

Provides explicit when-to-use guidance: for finding specific activity methods, experimental procedures, concept explanations, and cases that metadata search cannot find. Also advises using get_document_text for truncated excerpts. Notes first call is slow due to index building.

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