get_credentials

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

Annotations are absent, so the description carries the full burden of behavioral disclosure, and it provides none. It does not state whether the call is read-only, what data is returned, whether it triggers any side effects, or any security considerations.

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 words is under-specification rather than conciseness. The sentence does not earn its place because it repeats the name and communicates no decision-useful information.

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?

The tool is simple, but the meaning of 'credentials' is left fully ambiguous in a sibling space dense with credential-related tools. Without an output schema or annotations, the description alone cannot tell the agent what comes back, so it is not complete enough for correct selection and invocation.

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 100%, so the baseline is 3. The description is not required to duplicate the schema but adds no clarification about how 'domain' filters credentials or what format is expected.

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 'Get credentials' is a tautology that merely restates the tool name. It does not say what kind of credentials are returned, from which service, or how this differs from credential-adjacent siblings like get_cookies, get_csrf_token, and get_login_info.

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 call this tool versus alternative auth/credential tools in the sibling list. With several siblings that plausibly return credential-like data, the agent has nothing to select on.

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