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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context beyond annotations: parallel execution, maximum 6 queries, and that all matching objects are FULLY loaded so no follow-up call is needed. This helps the agent understand side effects and performance characteristics.

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 usage condition and alternative. It is somewhat long due to the trigger phrase list, but that list provides practical guidance. Overall it is structured and wastes little space.

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 read-only batch search tool with fully described parameters and safety annotations, the description covers everything needed: when to use, how it behaves, constraints, and follow-up guidance. No gaps remain for correct 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?

Schema coverage is 100%, and the schema descriptions are already clear about newline-separated queries, max 6, topK and topObjects meaning. The description reinforces the 'each line becomes one parallel search' idea but does not significantly add beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: runs multiple D365 searches in parallel, equivalent to search_d365_code. It explicitly differentiates itself from the sibling search_d365_code by covering the batch case, so an agent can select it confidently.

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?

The description opens with a WHEN condition and explicitly says to use it INSTEAD of multiple sequential search_d365_code calls. It also provides a list of trigger phrases and warns not to follow up with get_object_details, which gives clear selection and exclusion criteria.

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