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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: it discloses that no paid work is incurred, that times are UTC, and that imported knowledge is not treated as approved brand guidance — a data-provenance caveat an agent could not derive from structured fields.

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?

Four short sentences, front-loaded with the resource and payload before the cost, caveat and follow-up. Every sentence carries distinct information, though the UTC and 'no paid work' notes are terse enough that they read as fragments rather than fully integrated guidance.

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 values need no explanation, and the description covers scope, cost, timezone semantics, a provenance caveat and a recommended follow-up. The only gap is the absence of explicit sibling differentiation against the other read-only profile/context tools in this large family.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The statement 'No inputs' correctly confirms the empty schema rather than leaving it implicit.

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 opens with a specific verb and resource ('Read the current organization's business identity') and enumerates the exact payload: approved AI-profile reference/version and missing fields. That level of specificity separates it from adjacent read tools like webanto_get_context and webanto_get_capabilities without the agent needing to open a schema.

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 states the cost/effort profile ('No inputs, mutation or paid work') and gives an explicit next step: 'Follow with webanto_get_copy_proposal to inspect existing product copy.' What's missing is a negative rule — it never says when to prefer webanto_get_context or webanto_get_capabilities instead, so the agent must infer the boundary from names alone.

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