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

With no annotations, the description needs to carry the behavioral burden. It explains the return type (matching records with due date and status) and the verb 'search' implies a read-only operation. It does not explicitly state that no modifications occur or mention auth/rate limit requirements, but for a simple search tool this is a sufficient disclosure and adds more context than the schema alone.

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 two sentences with zero wasted words; it front-loads the action ('Search provider credentials...') and then specifies the return information. No extra fluff, repetitive phrases, or unnecessary context.

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?

The tool is a single-parameter, non-nested search with no output schema. The description explains both the search scope and the key return fields (due date and status), so an agent can call it without ambiguity. The schema alone documents the optional search-all behavior, and while the description could mention listing everything, that omission is minor.

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 describes the query parameter with 100% coverage, including case-insensitivity and shorthand. The description goes beyond the schema by enumerating specific targets (provider name, payer, credential type), giving the agent clearer guidance on how to construct query values that will match.

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 uses the specific verb 'Search' and clearly identifies the resource (provider credentials) and the search dimensions (provider name, payer, credential type). This makes it easily distinguishable from sibling tools like export_credentialing_report or get_credentialing_summary.

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 for searching credential records by those fields, but it does not explicitly say when to use this tool versus alternatives like get_credentials_due or list_billing_at_risk, nor does it mention any exclusion criteria. The presence of sibling tools makes explicit routing guidance valuable, but it's still implied context that a search function is appropriate.

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