get_account_data_tour

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

No annotations are provided, so the description carries the full burden. It states the tool returns a complex data structure but does not disclose behavioral traits such as idempotency, latency, or side effects. The term 'Return' implies read-only, which is adequate but not explicit.

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 extremely concise: two sentences with no filler. Every word adds value, efficiently communicating purpose, content, and deployment constraint.

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?

Despite lacking an output schema, the description enumerates key components of the returned tour (trust preflight, business pulse, etc.), providing sufficient context for an agent to understand the tool's output. The note about being a stub adds deployment context, though further structural details could be beneficial.

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 100% and both parameters have descriptions. The description does not add extra meaning beyond the schema, meeting the baseline for high coverage.

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 'Return' and clearly identifies the resource as a 'first-run account data tour' with concrete components (trust preflight, business pulse, etc.). It distinguishes from sibling tools which are standard CRUD operations, making its unique composite purpose evident.

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 description explicitly notes 'Hosted endpoint only; this local stdio server is an introspection stub,' providing a clear when-not (local use). While it doesn't name alternatives, the context implies this tool is for a specialized composite data view, not for standard data retrieval.

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