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

With no annotations provided, the description carries full burden, and it does well by explicitly stating that credential values are never returned and are write-only. It also discloses the response type (JSON), but does not mention error handling, pagination, or authentication requirements beyond the implied 'authenticated customer'.

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?

Two sentences, no wasted words. The first sentence packs the core purpose and output structure, and the second sentence adds a critical security caveat without redundancy.

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 simple no-parameter tool, the description covers the essential return values and the JSON format. It lacks details like sorting order or empty-list behavior, but these are minor given the tool's low complexity and the richness of the description relative to the empty schema.

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 tool has zero parameters, so the schema is trivially satisfied and the baseline is 4. The description adds meaning by explaining the output grouping and fields, which is helpful even though no parameter documentation is needed.

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 tool lists the authenticated customer's stored monitoring credentials, grouped by provider, with specific fields (provider name, key names, updated-at timestamp). This is a specific verb+resource combo that distinguishes it from sibling tools like list_api_test_credentials and list_investigation_alert_channels.

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 the tool is for viewing stored monitoring credentials but does not explicitly state when to use it over alternatives or provide exclusions. It lacks mentions of sibling tools such as list_api_test_credentials, leaving the agent to infer the distinction from the name and context.

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