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

No annotations are provided, so the description carries the burden. It discloses that results are semantically ranked and capped at top-N, plus the org-wide-vs-workspace scoping default, but says nothing about permissions, result ordering guarantees, or what 'relevance' means. Adequate but with clear gaps for a read tool with zero annotation coverage.

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 short sentences, front-loaded with the core action and followed by the return shape and usage trigger. Every sentence earns its place with no redundancy.

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 no output schema, the description conveys the return concept ('top-N most relevant files') and the intended workflow. The filter object's fields are left to the schema, which covers them adequately; only deeper result semantics are absent.

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 coverage is 75%, so most parameters (query, top_k default/max, workspace_id scoping) are already documented in the schema. The description adds no parameter-level detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb+resource: 'semantic search across your org's artifacts in AgentDrive' and adds the return shape ('top-N most relevant files'). This is clearly distinguishable from sibling list/read tools like drive_list and drive_read, though it never names them explicitly.

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?

Gives an explicit when-to-use trigger: 'Use this BEFORE writing similar artifacts to avoid duplication and surface prior context.' That is clear actionable context, but it does not mention alternatives or when-not-to-use (e.g., vs drive_list for exact listing).

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