My BI.ZONE profile

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

With no annotations, the description carries the full burden and does disclose the auth mechanism (BIZONE_SESSIONID / BIZONE_COOKIE) and a meaningful privacy boundary ('reports themselves are never exposed'), which prevents an agent from expecting report data. It stops short of describing behavior when no session is configured or any error/failure mode.

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?

Two sentences, front-loaded with the resource and its data source, followed by the privacy caveat. No filler or 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?

With no output schema and no annotations, the description compensates by enumerating the returned fields (username, reputation, resolved reports, rewards, verification state). The main remaining gap is undefined behavior when the session is missing or invalid.

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; baseline 4 applies. The mention of session env vars is a useful hint that the caller's context, not an argument, drives the result.

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 and resource (returns the profile of the session-configured account) and enumerates the fields returned. It implicitly distinguishes itself from get_researcher by scoping to the authenticated account, though it never names that sibling explicitly.

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?

Usage is only implied: an agent can infer this is the way to identify the current account, but there is no explicit 'use this when...' guidance or pointer to get_researcher for other users. No exclusions or prerequisites are stated beyond the session env vars.

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