glob

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: gitignore filtering is on by default and toggled by respect_gitignore=false, and results are paged via offset. It omits that results are capped at max_results=500, which affects how an agent pages.

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 purpose, each carrying distinct information (pattern semantics, gitignore default, paging). No filler.

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?

An output schema exists so return shape need not be described, and the essential call mechanics are present. The remaining gap is the undocumented max_results cap and the lack of explicit routing against the many sibling search/listing tools.

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 0%, so the description must carry the load: it explains pattern, path (relative base), offset (paging), and respect_gitignore. It says nothing about max_results (default 500), leaving the truncation cap — arguably the most consequential parameter — undocumented in both places.

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 and resource ('Find files by glob pattern') with a concrete example pattern and the base-path semantics. It is clearly distinct from grep/search_workspace_text (content search) by implication, but never names those siblings to make the distinction explicit.

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 real usage facts — gitignored files are skipped by default, and offset is the paging mechanism — but never says when to prefer this over list_directory, grep, or search_workspace_text. Usage is implied rather than guided.

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