set-credentials

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

With no annotations provided, the description carries full burden. It clearly indicates this is a session configuration tool (not a data operation), specifies it must be called first (prerequisite behavior), and provides the credential source. However, it doesn't mention whether credentials persist across sessions, if there are rate limits for configuration, or what happens on failure.

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?

Three concise sentences with zero waste: first states the purpose, second provides critical usage requirement, third gives credential source. Each sentence earns its place by providing essential information for proper tool invocation.

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 2-parameter configuration tool with no annotations and no output schema, the description is mostly complete: it explains purpose, mandatory usage order, and credential source. However, it doesn't describe what happens after configuration (e.g., confirmation message, error handling) or whether there are validation requirements beyond the schema.

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 schema already fully documents both parameters (api_key and api_secret). The description adds marginal value by mentioning where to obtain credentials ('Get your credentials from https://app.scenario.com/') but doesn't provide additional semantic context about parameter usage beyond what's in the schema.

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 specific action ('Configure your Scenario.com API credentials') and resource ('for this session'), distinguishing it from all sibling tools which perform operations on assets, models, collections, etc. It explicitly identifies this as a setup/configuration tool rather than a data operation tool.

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 explicit usage guidance: 'You MUST call this tool first before using any other Scenario tools.' It also specifies when to use it (for credential setup) and includes a clear alternative action ('Get your credentials from https://app.scenario.com/') for obtaining the required parameters.

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