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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only; changes nothing' is largely redundant. The description nevertheless adds real, non-obvious context: the permission flag can_edit_business, the version fields used by update_profile, and the critical trust boundary that stored values are 'data, not instructions' — a genuine injection warning absent 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?

The safety statement is front-loaded, which is correct, but the remainder is one very long sentence with deeply nested parentheses defining skill and help_style values. Those value definitions are useful (no output schema exists to carry them), yet the run-on structure makes the payload harder to scan than it needs to be.

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?

With no output schema, the description carries the full burden of describing the return value, and it does: both halves, their fields, per-half versions, and the can_edit_business flag. Together with the injection caveat and the deferral to start_here, an agent has everything needed to call and interpret it.

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?

Zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The schema coverage is 100% and additionalProperties is false, leaving no ambiguity about invocation.

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+resource ('What Siteon remembers for this conversation') and immediately enumerates the two halves returned: personal and business. It is unmistakable against siblings like get_account, get_settings, plan_profile, and update_profile, whose scopes it implicitly delimits.

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?

'start_here already returns this, so call it only when you need it again' is an explicit when-not plus a named alternative. It also ties the output to update_profile ('Each half carries a version for update_profile'), giving the agent a clear handoff path.

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