Get Document by Title

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

With no annotations, the description carries full burden. It transparently explains that the tool performs two actions (search and export) and returns markdown content. It does not indicate any side effects or destructive behavior, which is consistent with a read operation. However, it could mention if any state changes occur.

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 consists of two efficient sentences. It is front-loaded with the main action and immediately distinguishes the tool from siblings. No extraneous information is present.

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 search-and-export tool with no output schema or annotations, the description covers the core functionality well. It lacks explanation of the 'workspaceId' parameter and does not describe the return format or error handling, but overall it provides sufficient context for basic usage.

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?

The schema covers 67% of parameters with descriptions. The tool description adds context like 'returns first match by default' but does not elaborate on 'workspaceId', which lacks schema description. The description adds minimal value beyond the 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 tool's function: find a document by title and return its content as markdown. It explicitly mentions combining 'search_docs' and 'export_doc_markdown', which distinguishes it from sibling tools. The default behavior and use of 'limit' are also specified.

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 implies usage as a convenience shortcut for search+export but does not explicitly state when to use this vs alternatives. No conditions or prerequisites are mentioned, such as when to use separate tools or if workspaceId is required.

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