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

No annotations are provided, so the description carries the full burden. It discloses the output format (CSV text) and content (provider, credential, due date, status, follow-up history), but does not mention any potential side effects, read-only nature, performance implications, or authentication requirements. For a simple export, this is adequate but not exhaustive.

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, well-structured sentence that front-loads the action ('Export') and the scope ('full credentialing report'). It efficiently conveys the output format and contents without redundancy, earning a perfect score.

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?

With no parameters and no output schema, the description must convey the return value, which it does by specifying the CSV fields. It is complete enough for an agent to understand what will be returned, though it could optionally mention the exact header order or note about large reports. Overall, it is sufficient for a simple export tool.

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?

There are zero parameters, and the schema coverage is 100% vacuously. The baseline for zero parameters is 4, and the description adds no parameter information because none exist, which 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 (export), a specific resource (full credentialing report), and the output format (CSV text) with a list of included fields. It clearly distinguishes itself from siblings like get_credentialing_summary (summary) and get_credentials_due (due list) by focusing on the complete export.

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 this is for a comprehensive export, but it does not explicitly state when to use this tool versus the sibling tools like get_credentialing_summary or get_credentials_due. There is no explicit 'use this when' or 'prefer that when' guidance, leaving the selection to inference from the term 'full report'.

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