yd_set_client_id

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

No annotations are provided, and the description only states 'Save' and 'return authorization link', without disclosing details such as whether it overwrites existing data, requires authentication, or has side effects. The behavioral inference is minimal.

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, well-structured sentence that front-loads the primary action and then provides necessary context. No extraneous information is present.

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 the tool's role in OAuth setup, the description covers key prerequisites (scopes, redirect URL), the required parameter, and the output (authorization link). While it could mention the subsequent need for a token, the tool's scope is limited to saving the client_id, so it is largely 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 coverage is 100% with clear descriptions for both parameters. The description adds value by providing the authorization link context and registration instructions, but the schema already covers parameter meaning adequately, so the baseline of 3 is appropriate.

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 'Save the Yandex OAuth application client_id' and the outcome 'return the authorization link', distinguishing it from siblings. The context of registering an app with specific scopes and redirect URL reinforces the purpose.

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 clear context for when to use the tool (to save client_id and get authorization link) and prerequisites (registering an app with scopes). However, it does not specify when not to use it or mention alternatives like yd_set_token, which may be relevant for subsequent steps.

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