profilarr_list_databases

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

The description adds the noteworthy behavior that secrets are stripped from the response (personal_access_token replaced with hasPat). This goes beyond the readOnlyHint annotation, providing valuable insight into the tool's data redaction behavior.

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 concise sentence of 11 words, front-loaded with the action and resource. Every word contributes meaning, with no fluff.

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 parameterless list operation with an output schema and readOnly annotation, the description fully covers the essential behavior. The secret-stripping note addresses the only potential surprise, making the description complete.

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 no parameters, so the description does not need to explain them. It adds value by clarifying the output semantics (secrets stripped), which is useful for the agent.

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 a specific verb 'List' and a specific resource 'linked PCD databases', clearly distinguishing from sibling tools like get_database or list_announcements. It precisely states the tool's function.

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 clarifies when to use this tool (to list all linked PCD databases) and implicitly contrasts with get_database for individual retrieval. It does not explicitly name alternatives but the context is clear.

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