get_home_feed

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered structurally. The description adds the useful constraint that no engagement actions are performed, which prevents the agent from expecting post/like/retweet behavior. It does not add pagination or ordering 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?

A single efficient sentence with the core action front-loaded and no filler. It is very terse, but nothing is wasted.

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?

An output schema exists, so return values needn't be explained. However, with 0% schema description coverage on two params and no usage routing, the description is only minimally adequate for a tool whose 'account' parameter carries the real invocation risk.

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 0% – neither 'limit' nor 'account' is documented in the schema or the description. The description gives no meaning for 'account' (which account context?) or the default limit of 20, leaving both parameters to be inferred.

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 ('Read') and resource ('posts currently visible in the home feed'), so it's clear what the tool returns. It distinguishes itself lightly from engagement tools via 'no engagement actions', but does not name a specific sibling to route the agent.

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 engagement actions' implies the tool is read-oriented and hints the agent should reach for engagement tools elsewhere, but there is no explicit when-to-use context or named alternative among the many sibling read tools (get_profile_posts, search_tweets, get_notifications). Usage is only implied.

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