auth_profiles

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

No annotations are present, so the description carries the behavioral disclosure burden. The note that 'secrets are never shown' is a valuable behavioral guarantee. However, the description does not disclose the return payload shape, behavior for nonexistent profiles, or explicitly confirm zero side effects.

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 compact sentence with the core behavior front-loaded. The parenthetical secrets note earns its place and there is no filler or 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 one-parameter read operation, the description is mostly adequate. However, with no output schema, it omits the return shape and any behavior for unknown or missing profile names. The secrets redaction note helps, but some operational uncertainty remains.

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 must compensate. The phrase 'show one' implies that the optional name parameter selects a specific profile, but the description never explicitly states that name is the profile identifier or what happens when it is omitted beyond the implied list behavior.

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 clear verb and resource: 'List auth profiles, or show one.' This makes the tool's purpose immediately identifiable and distinguishes it from auth siblings like auth_update_profile, auth_delete_profile, and auth_check, which perform different actions.

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 says what the tool does but does not specify when to use it over alternatives such as auth_check or auth_update_profile. There are no explicit conditions, exclusions, or guidance about when showing one profile is preferable to other auth operations.

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