ads_store_status

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

With no annotations, the description carries the full burden; "Show" implies a read-only inspection, which is consistent with a status tool, and it lists the categories of information surfaced. However, it never explicitly states that it is non-mutating, whether it is cheap or expensive to call, or what the response looks like.

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?

A single efficient sentence with the action verb front-loaded and no filler. It is appropriately sized, though the three-item list is terse enough that a little more framing could be added without waste.

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 zero-argument diagnostic tool with no annotations and no output schema, the description does list the kinds of values returned, which partially compensates. But "safety defaults" is vague and it gives no sense of what an agent should do with the output or when it matters.

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?

The schema is an empty object with zero parameters, which per the baseline warrants a 4. The description correctly implies a no-argument call, and there is nothing parameter-related left to document.

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?

States a specific verb ("Show") and a concrete resource (local SQLite storage path, row counts, safety defaults), so an agent knows exactly what the tool returns. It doesn't explicitly distinguish itself from status siblings such as ads_dstore_status or ads_network_status, but "local SQLite storage" is a reasonably distinct scope.

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 statement of when to call this versus the many other *_status tools, and no mention of prerequisites or follow-up actions. The phrase "safety defaults" hints at a pre-flight/diagnostic role, but the agent has to infer that connection.

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