Find Doc by Title

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

No annotations provided, but the description fully discloses behavior: it reads workspace metadata, is fast with no per-doc fetch, case-sensitive by default with option for case-insensitive, and returns up to limit matches. No contradictions.

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 mostly concise, front-loaded with purpose. However, the return structure is embedded within the text, making it slightly dense. Still, 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?

Given no output schema, the description fully explains the return format (matches with specific fields, query, workspaceDocCount, truncated). All parameters are handled, and the tool's behavior is well-documented. Complete for its complexity.

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?

Input schema has 100% description coverage, but the description adds significant value: clarifies defaults (limit=50, caseInsensitive=false), workspaceId optional context, and explains return shape which compensates for missing output 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 it resolves docs by exact title and returns all matches up to a limit. It distinguishes itself from search_docs by specifying case-sensitivity and higher limit, which clarifies its specific purpose.

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?

Explicitly compares to search_docs, stating when to prefer this tool (exact title, case-sensitive, higher limit). Provides clear context for when to use and when not to use.

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