d365fo_search_profiles

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

No annotations are provided, so the description bears full responsibility. It correctly describes a read-only search operation returning a dictionary, which aligns with typical search behavior. However, it lacks details on authentication requirements, rate limits, or potential side effects, though none are expected.

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 well-structured with clear sections (title, Args, Returns). It is concise, with no superfluous sentences, and front-loads the core purpose. Every element earns its place.

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?

Given the output schema exists (context signals), the description's 'Returns' summary is adequate. All three parameters are thoroughly explained, and the tool's purpose is fully covered for a search operation. No gaps remain for effective use.

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 compensate. The 'Args' section explains each parameter clearly: 'pattern' for matching, 'hasCredentialSource' for filtering by credential presence, and 'credentialSourceType' for filtering by type. This adds significant meaning beyond the bare schema names.

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 clearly states the action ('Search') and resource ('D365FO environment profiles'). It distinguishes from sibling tools like 'd365fo_list_profiles' (which lists all profiles without filtering) and 'd365fo_get_profile' (retrieves a specific profile by ID), making the purpose unambiguous.

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 implies usage when specific profile criteria need to be applied, but it does not explicitly state when to use this tool versus alternatives (e.g., 'list_profiles' for unfiltered listing or 'get_profile' for exact match). No when-not-to-use guidance or alternatives are given.

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