Who am I

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does convey a read-only implication via 'Return' and the GET endpoint, and it indicates authentication is involved ('authenticated account', 'confirm auth is working'). However, it does not disclose potential failure modes (e.g., unauthenticated requests), rate limits, or explicitly confirm there are no side effects, leaving some ambiguity.

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 two concise sentences. The first states the core function and endpoint, and the second adds a use case. There is no redundant phrasing or unnecessary detail, making it efficient and front-loaded.

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?

For a simple tool with one optional parameter and no output schema, the description adequately covers purpose, use case, and the endpoint. It does not elaborate on return value structure or error handling, but the phrase 'return the authenticated account/identity' gives a reasonable sense of the output. Given the tool's low complexity, this is nearly complete.

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 input schema covers the single parameter (organization) with a clear description: 'Organization slug. Defaults to WFLOW_ORG.' The description text adds no additional meaning to the parameter, but with 100% schema coverage the baseline is 3. No further elaboration is necessary here.

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 clearly states the tool's function: 'Return the authenticated account/identity for an organization' and provides the underlying HTTP endpoint '(GET /account)'. The verb 'Return' and the resource 'authenticated account/identity' are specific and distinguish this from sibling tools like wflow_list_users or wflow_get_user which deal with user listings rather than the acting identity.

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 provides clear usage context: 'Useful to confirm auth is working and see the acting user.' This tells the agent when to invoke this tool. It does not explicitly mention alternatives or when not to use it, but the guidance is sufficient for a simple identity-check tool.

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