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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds the behavior an agent actually needs to know before calling: the account must be authenticated, and this is a free read that consumes no research credits and returns no source data.

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, zero filler, with the identifying purpose front-loaded and the billing/scope qualifier second. Every clause carries information an agent can act on.

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 parameterless read with an output schema and full annotation coverage, this is sufficient: what it returns is sketched in the description and formally defined by the output schema, and auth plus cost context is stated. Nothing required to call it correctly is missing.

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 no parameter semantics to explain; the baseline for a no-parameter tool is 4. The description appropriately spends its words on output identity rather than inventing parameter behavior.

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 ("Identify") and resource ("the connected CryptoSocials account") and names the fields returned (account ID, display name, email), which clearly separates it from the research-oriented siblings. The phrasing "by its stable account ID, display name and email" is mildly ambiguous — it could be misread as input identifiers even though the schema has no parameters — but the intent is recoverable.

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?

Adds real routing context: "Free authenticated account read; not a research-credit or source-data request" tells the agent this call is cost-free and is not the path to research credits or evidence data. It lacks an explicit named alternative (e.g., get_usage, get_research_balance), so it falls short of full when/when-not guidance.

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