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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The only added claims are 'bounded' and 'paginated', but both are already encoded in the schema (head_limit maximum of 500, cursor parameter) and neither is explained — no statement of what the bound is, how pagination terminates, or what happens on truncation.

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?

Five words are certainly compact, but this is under-specification rather than conciseness — nothing is front-loaded because nothing substantive is stated. The space saved buys no clarity.

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?

A 13-parameter search tool with no output schema, no parameter documentation, and only generic safety annotations demands far more from its description than one clause. An agent cannot reliably construct a call to this tool from what is written here.

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?

With 13 parameters and 0% schema description coverage, the description must carry the meaning of pattern, glob, path, build_id, workspace, output_mode, and the context/include flags. It mentions none of them; 'bounded, paginated' gestures vaguely at head_limit and cursor without explaining either.

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 fragment 'Bounded, paginated source search' does convey a verb (search) and a rough resource (source), but 'source' is never defined — an agent cannot tell whether it means source files in a build, workspace files, or repo contents. It also makes no attempt to distinguish itself from nearby siblings such as files_list, files_read, or components_search.

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 statement of when to use this tool, when not to, or which sibling to prefer for listing versus reading versus searching. The agent is left to infer usage entirely from the name.

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