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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: it only touches the active tenant, it requires specific opt-in permission scopes, and it is gated by the registered module authority. The phrasing is terse and jargon-heavy, but it discloses auth and scope behavior the annotations do not.

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 with the verb front-loaded and no filler prose, which is good. However the second sentence is a dense negation chain ("arbitrary metadata, other tenant, campaign/send authority or document reissue") that costs the reader more parsing effort than the information it delivers.

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?

This is a zero-parameter read with no output schema, so the description's main remaining duty is to say what comes back, and it never does beyond "structured settings." Combined with the unexplained expectedRevision reference, an agent has no picture of the response shape or how to use it in a follow-up step.

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?

With zero parameters the baseline is 4, but the description explicitly says the read requires an "exact expectedRevision" while the schema declares an empty object with additionalProperties=false — there is no such input. That mismatch is actively confusing rather than merely redundant, so it is penalized below the no-param baseline.

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 verb is clear ("Read") and the scope is narrowed to "the active tenant," but the resource is described only as "structured settings," which does not tell an agent what a business model actually contains versus get_business_catalog or get_company_profile. The trailing scope-negation list hints at boundaries without ever stating the tool's content, so an agent cannot confidently distinguish it from siblings.

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?

"Separate opt-in business:read/brand:read and current registered module authority" implies prerequisites but never says when to call this instead of prepare_business_model_change or the other read siblings. The negatives ("No arbitrary metadata, other tenant, campaign/send authority or document reissue") are scope limits rather than when-to-use guidance, leaving selection to inference.

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