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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: 'no signature' tells the agent no signing/auth step is required, and it clarifies that results can vary by caller. It stops short of explaining return volume or pagination.

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?

Three short clauses, front-loaded with the core action and then the notable behaviors. Minimal waste; the caller sentence is slightly redundant with the parameter name but still earns its place.

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 single-optional-parameter read tool with full annotation coverage and no output schema, the description supplies the key facts: what the feed contains, that it is unsigned/read-only, and how caller changes the result. Only the absence of sibling differentiation and any hint at result volume keeps it from being complete.

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 baseline is 3, and the description adds real semantic value: it explains the default (the caller's own view) and that passing caller yields caller-dependent results, which the schema's terse 'run the query as' does not convey.

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 ... feed') plus the content scope ('posts from accounts it follows'), which distinguishes it from messaging inbox tools. However, it never distinguishes itself from the very similar sibling geode_social_get_paid_feed, leaving the agent to guess which feed variant applies.

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 when-to-use or when-not guidance is given, and the obvious alternative (geode_social_get_paid_feed) is not named or contrasted. The only guidance present is about the caller parameter, not about selecting this tool over siblings.

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