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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds 'anything that buys, sells or writes refuses,' reinforcing the read-only nature, and notes 'their data comes back as it is,' but these are generic to the operator rather than specific to this tool. 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?

The description is concise, leading with the core purpose. Some context (server hosting, 'live seat on The Wall') is tangential but not excessive. The read-only note is useful. Overall it is well-structured and front-loaded.

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 simple status tool, the description covers the core function and read-only constraint. However, it omits the return format (no output schema) and leaves slight ambiguity about authCode requirement (schema shows 0 required but description implies it may be needed). This gap prevents full completeness.

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% and the parameter authCode is fully described in the schema property. The tool description adds no additional parameter context, so baseline 3 applies since the schema handles parameter documentation.

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?

The description clearly states the tool shows whether X is connected and if tweet.write is granted, which is a specific verb+resource. It also positions itself as read-only, distinguishing it from potential write tools like orbitx_x_connect. The purpose is unambiguous and directly actionable.

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?

The description implies usage (checking connection/status) and notes the read-only constraint, but does not explicitly contrast with sibling tools like orbitx_x_connect or specify when to use this instead of alternatives. The guidance is general rather than tool-specific.

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