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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds a genuinely useful consent/default-off rule, but it does not disclose what turning the check off does to existing data, whether enabling triggers external or billable searches, or what happens to the submitted question.

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 short sentences, front-loaded with the action and followed by the guardrail; nothing is padded. It is arguably under-specified rather than over-long, but on the conciseness axis it is efficient.

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 mutating, open-world, destructive-flagged toggle with no output schema, the description leaves out what enabling actually does, what gets lost on disable, and the role of the "question" parameter. The consent rule is helpful but the definition is not complete enough for confident 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 adds nothing about the two parameters — notably the optional "question" ("A question a buyer might ask") is never mentioned, so the agent gets no sense of whether it is required for the check to be useful.

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 gives a verb plus resource ("turn the weekly search check on or off"), which is more than a restatement of the name, but "weekly search check" is unexplained jargon that never ties back to article tracking, and no distinction is drawn from nearby siblings such as soclo_articles_checks or soclo_articles_check_run.

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?

"It stays off until the owner asks for it" is a real usage constraint that tells the agent not to enable it unprompted, which is more than implied guidance. However, it never names an alternative (e.g. running a one-off check vs. subscribing) or says when to turn it off.

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