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

With no annotations, the description carries the full burden but does add real context: 'null when off' discloses the return behavior and 'Owner or office' signals the required role. It never explicitly says this is a read-only accessor or what happens on missing/unset configurations, leaving a gap for an unannotated tool.

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?

It is a single compact sentence with no filler, which is good. However, the phrasing is clipped to the point of ambiguity — 'Owner or office' is unexplained and the action verb is absent, so brevity costs clarity rather than earning it.

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?

An output schema exists, so return shape needn't be re-explained, and the description usefully adds null-when-off semantics plus a permission hint. Still, for an unannotated tool the description should confirm the read-only nature and clarify what 'Owner or office' means before an agent can call it confidently.

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 0% and the single parameter (shop_id, uuid) is never mentioned in the description. The description adds no meaning about whose shop is queried or any scoping nuance beyond the schema's type declaration.

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 names the resource ('the shop's profit alert: the margin floor in percent') but never states the action (read/get). The sibling costs_setMarginAlert makes a retrieval interpretation plausible, yet the agent must infer the verb from the name rather than the description.

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 costs_setMarginAlert or costs_job/costs_jobs. The only hint is the value semantics ('null when off'), which does not route the agent between siblings.

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