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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action and does not mention return format, whether it returns content or metadata, matching behavior (exact vs fuzzy), or error handling when no file is found. This is a significant gap for an agent to understand expectations.

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 concise sentence that front-loads the verb 'Find' and directly states the search criterion. It contains no fluff and is appropriately sized for the tool's simplicity.

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?

While the tool is simple, the description leaves critical information unstated: what is actually returned (file content, path, or reference), what happens if no match exists, and how exact the topic match must be. With no annotations or output schema, this brevity makes the tool insufficiently defined for confident invocation.

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 has a single required 'topic' string with no description. The description adds 'by topic name', which clarifies that the parameter is the topic's name, but it does not explain accepted formats, whether search is case-sensitive, or any other parameter nuances. Given the 0% schema description coverage, the description should compensate more.

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: finding a knowledge file by topic name. It uses a specific verb and resource, and it distinguishes itself from siblings like get_knowledge_index (which likely lists all knowledges) and save_to_knowledge (which writes).

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?

There is no guidance on when to use this tool versus alternatives, such as get_knowledge_index for browsing or search tools for full-text search. The description does not mention any exclusions or preferred contexts, so the agent is left without usage direction.

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