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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool lists items due within a time window and mentions the default, but it does not disclose potential limitations (e.g., pagination, result limits, or behavior when no results exist). It implies a read operation but does not explicitly state it. This is adequate but not thorough.

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 a single, front-loaded sentence that immediately states the verb and resource, then adds the time window and examples. There is no filler or redundant information beyond the default, which is also in the schema but is harmless. It is concise and well-structured.

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 tool with one optional parameter and no output schema, the description is largely complete. It states what is listed, the time window, and the default, and even enumerates specific item types. However, it does not specify the return format (e.g., whether it returns full records or just counts) or any edge-case behavior, which a fully complete description might include. Given the simplicity, this is a minor gap.

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 already describes the 'days' parameter including its default value ('default 90'). The description's mention of 'default 90' is redundant with the schema, so it adds no new meaning. Baseline 3 is appropriate because the schema already carries the parameter semantics.

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 verb 'List' and the resource 'credentials and payer cycles due within the next N days', and adds specifics like 'CAQH attestations and re-credentialing packets'. It is not a tautology and provides concrete scope, but it does not explicitly differentiate from sibling tools like get_credentialing_summary or search_credentials, so it misses the full 5.

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 gives no guidance on when to use this tool versus its siblings. It does not mention alternatives, exclusions, or conditions. The only contextual hint is the default time window, which is a parameter detail rather than usage guidance.

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