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

Annotations only declare readOnlyHint=true, but the description adds important behavioral context: queries run in parallel, each line becomes one search, results are fully loaded with all chunks, and no follow-up detail fetch is needed. This goes well beyond the annotation and prevents redundant agent actions.

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 front-loaded with the key WHEN/INSTEAD message, followed by capacity limits, behavioral equivalence, and a clear anti-pattern. The trigger list is somewhat long but earns its place by helping the agent recognize when to choose this tool.

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 multi-query search tool with no output schema, the description sufficiently covers when to use it, how queries map to searches, limits, result equivalence, and post-call behavior. An agent has everything needed to invoke it correctly and avoid unnecessary follow-up calls.

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 already covers all parameters with descriptions, so the baseline is 3. The description adds meaning by clarifying that each newline-separated query becomes a parallel search, enforcing the max 6 behavior, and explaining that topObjects controls full-chunk loading per query.

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 purpose: run multiple D365 object/concept searches in parallel. It explicitly says results are equivalent to search_d365_code but returned together, distinguishing it from the closest sibling without ambiguity.

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?

Provides explicit when-to-use guidance, tells the agent to use it INSTEAD of multiple sequential search_d365_code calls, sets a maximum of 6 queries per call, and even lists concrete trigger phrases. It also warns not to follow up with get_object_details because objects are fully loaded.

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