XMLStock: set credentials

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

Goes well beyond the readOnlyHint=false annotation by disclosing the exact file path, the 600 permission mode, live application without restart, multi-account suffix behavior, and response masking. This gives an agent a precise model of the side effects without needing to inspect the environment.

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 dense sentences carry the core action, side effects, usage rule, and response behavior with no filler. Critical information is front-loaded at the beginning, and every clause earns its place.

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 an optional-parameter mutation tool with no output schema, the description covers persistence location, permissions, activation behavior, updates-only guidance, multi-account handling, and output masking. Nothing an agent needs to invoke it correctly is missing.

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%, so parameters are already documented. The description adds value by clarifying update semantics ('only fields to update'), the account profile suffix behavior, and that user-supplied values are masked in responses, which the schema does not convey.

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?

Description opens with a specific verb and resource: 'Сохранить ключи xmlstock в /root/.config/seo-tools-mcp/.env (права 600)' and adds the immediate-apply behavior. It clearly identifies this as the credentials-setting tool among siblings that are all data/query tools, so there is no ambiguity.

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?

Gives clear operational guidance: 'Передавать только обновляемые поля' and explains the account parameter's role in multi-account profiles. It does not explicitly say when to prefer this over alternatives, but no sibling performs credential writing, so the usage context is already unambiguous.

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