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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), but the description adds genuinely new context: 'no signature' discloses an authentication/cost requirement, and 'caller-dependent results' warns that output varies by viewer. The pagination sentence largely restates the schema rather than adding behavior.

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?

Front-loaded with the resource description and only three compact sentences. The pagination clause duplicates schema metadata and could be trimmed, but overall there is little waste.

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, the description usefully enumerates the returned fields and notes pagination, so an agent can anticipate the response shape. The main completeness gap is the absence of any disambiguation against the overlapping social-profile sibling.

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%, so the baseline is 3, but the description adds real meaning: it explains `caller` as 'the account whose view to read' rather than merely 'run the query as', which clarifies why results can differ. Pagination defaults/max are repeated from the schema rather than extended.

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 ('Get an account's Geode profile') and enumerates the returned data (display name, location, tags, bio, links, linked app accounts), so the agent knows exactly what this returns. However, it does nothing to distinguish itself from the near-identical sibling geode_social_get_account_profile, which is a real selection risk.

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?

There is no explicit when-to-use guidance and no named alternative. The only conditional language is the `caller` note ('for caller-dependent results'), which describes a parameter rather than when this tool is the right choice over geode_social_get_account_profile or geode_account_info.

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