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

The readOnlyHint annotation already covers the safety profile, and the description adds useful behavioral context: it reads a synced archive (hence fast but potentially stale), returns newest-first ordering, and may surface a connection link when no account is connected. No contradiction with annotations.

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 sentences with no filler. The output scope is front-loaded, the staleness caveat is placed second, and the query/error-handling behavior is stated last. Every sentence contributes useful information.

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 zero-required-parameter read tool with no output schema, the description covers what is returned, ordering, filtering, the sync caveat, and the no-account fallback behavior. An agent has enough to decide when to call it and what to do with the result.

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 description coverage is 100%, so the schema already documents limit, query, and handle fully. The description re-states that query filters tweet text, but adds no new meaning beyond the parameter names and schema descriptions.

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 resource ('the user's own tweets'), a clear verb ('get'), and precise characteristics (newest first, from connected X accounts, includes text, metrics, date, link). This differentiates it from siblings like search_tweets (which searches external tweets) and get_my_linkedin_posts (a different platform).

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?

Provides clear context: this reads the user's own connected-account tweets, not general tweets, and warns that a brand-new connection may not have synced yet. It includes an error-handling instruction for the no-account-connected case, but does not explicitly name alternatives or state when NOT to use this tool.

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