refresh_connection_credentials

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

The description discloses that the operation is a forced refresh (implying proactive action) and that the output excludes secrets, which is useful. However, with no annotations provided, it does not reveal potential side effects (e.g., invalidation of existing tokens), error behavior, or permission requirements. The description adds some transparency but leaves significant behavioral aspects implicit.

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, focused sentence that front-loads the primary action and output constraint. It is concise with no filler words, earning a high score for efficiency.

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?

While an output schema exists (so return format is partially covered), the description lacks critical context: no parameter semantics, no side-effect warnings, no usage conditions, and no annotation support. For a tool that forces a refresh, an agent would benefit from knowing prerequisites or failure handling. The description is only minimally 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?

Schema description coverage is 0%, so the description must compensate for the lack of parameter explanations. The description does not mention environment, connection_id, or provider_config_key at all. Since these parameters are undocumented in both the schema and the description, the agent receives no semantic guidance on what values to provide.

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 action ('Force an OAuth refresh') and the output ('return only a non-secret credential summary'). It is specific and distinguishable from siblings like get_connection or delete_connection, which do not force a refresh or restrict output to non-secret data.

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?

There is no guidance on when to use this tool versus alternatives like get_connection or delete_connection. No prerequisites, exclusions, or recommended contexts are mentioned. The description solely states the operation without any usage direction.

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