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

Since no annotations are provided, the description is responsible for all behavioral disclosure. It only specifies the action (on/off) but fails to disclose operational behavior, such as expected latency, idempotency, or system status upon completion.

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 perfectly concise, presenting the action and the critical scope constraint in a single, direct sentence without any extraneous wording.

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?

The description is complete enough for an agent to understand the core functionality and call the tool without further clarification. Given the low complexity and the lack of formal annotations, the description fulfills its immediate purpose.

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 0%. While the description mentions the action, it does not provide semantic meaning for the parameters themselves. It gives no insight into the required format of the 'shop_id' beyond what the schema provides, thus failing to compensate for the lack of structured detail.

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 uses a specific verb ('Turn') and clearly identifies the resource being manipulated ('owner's morning email'). It is perfectly clear what the function accomplishes.

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 definition provides a clear constraint on usage by noting it is restricted to 'owner only.' However, it does not advise on when this setting should be toggled versus other available reports or configuration options.

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