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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true. The description adds a little beyond that: 'no signature' indicates no crypto signing is required, and it enumerates the returned content. It does not cover pagination or rate limits, so a moderate score is warranted.

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-loads the verb+resource and contents, then appends behavioral ('Read-only; no signature') and parameter notes. Compact and well-ordered with no wasted sentences.

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 return contents (username, followers, following, posts) and confirms read-only semantics. It is largely complete for a simple two-param read, though sibling disambiguation 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?

Schema coverage is 100%, so both parameters are already documented. The description reframes 'caller' as 'the account whose view to read (for caller-dependent results)', which adds a useful nuance about view-dependence, but this is marginal beyond the schema.

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 (Get) and resource (account's Social profile) and enumerates what the profile contains (username, followers, following, posts). However it does not differentiate from the similarly-named sibling geode_profile_get_account_profile, so an agent must infer the 'Social' namespace distinction on its own.

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?

No explicit when-to-use guidance and no comparison to alternatives, despite a confusingly similar sibling (geode_profile_get_account_profile) and related social reads (get_account_following, get_public_feed). The caller note hints at a use case but does not frame selection criteria.

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