List OAuth2 Client Credentials

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

With no annotations, the description must fully disclose behavior. It states 'metadata only', indicating a safe, non-destructive read operation. However, it does not mention authentication requirements, permissions, any side effects, or pagination behavior (the 'top' parameter hints at pagination). The description is minimal but not misleading.

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, clear sentence with no unnecessary words. It is front-loaded and easy to parse.

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?

Given no output schema, the description should clarify what 'metadata' includes and any sorting or filtering. It does not mention that results might be paginated via 'top'. The overall completeness is adequate for a simple list operation but lacks detail expected for full agent comprehension.

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 description coverage is 0%, so the description should explain parameters. The only parameter 'top' is not mentioned in the description. An agent cannot infer that it controls the maximum number of returned artifacts.

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 specifies the verb 'List', the resource 'deployed OAuth2 Client Credential security artifacts', and the scope 'metadata only'. It distinguishes from sibling list tools by naming the exact artifact type.

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 provides no guidance on when to use this tool versus the many sibling list tools, nor does it mention any prerequisites or alternatives. The context of sibling tools includes similar list operations, but the description lacks explicit usage recommendations.

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