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

With no annotations, the description carries the full burden. It discloses the HTTP method (GET) and scope (account_info) and frames it as a probe, but does not explain what happens if unauthenticated, whether the call has side effects, or what profile data is returned in the absence of an output schema.

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 short clauses, front-loaded with the core purpose and followed by the endpoint and usage note. Every phrase contributes without redundancy.

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 low-complexity tool with one optional parameter and no output schema, the description covers the essential purpose and when to run it. It could optionally mention expected behavior on auth failure, but the core information needed to invoke it is present.

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 description coverage is 100%, so the parameter's meaning is fully documented in the schema. The description adds no additional parameter context, which is acceptable given the schema's completeness, but it does not enrich the understanding of the optional notification_message's role in follow-up failures.

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 states a specific function: an auth probe and profile summary, with the concrete endpoint 'GET profile/info scope account_info'. It differentiates itself from siblings like login/logout by being a probe rather than a session action, though it doesn't explicitly contrast with them.

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 phrase 'Run before authenticated flows' gives a clear when-to-use directive. It lacks explicit exclusions or alternative recommendations, but the context is sufficiently clear for an agent to know it is a prerequisite check.

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