social_media_posting_get_twitter_profile

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is well-covered. However, the description adds no extra behavioral context beyond the act of fetching. It does not describe what data is returned, potential failure modes (e.g., missing account), or any side effects, but given the annotations, this is acceptable for a read operation. No contradiction is present.

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 just one short sentence with no fluff. It is perfectly concise and the intent is front-loaded. Every word carries meaning, making it an example of efficient writing.

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?

Given the tool's simplicity (two parameters, both documented) and annotations that cover safety, the description is minimally sufficient. However, it lacks context about what 'profile' entails, whether an account must be pre-attached, and what the response will look like. In a landscape of many similar 'get_*_profile' tools, the description alone doesn't fully equip an agent to decide when to call it, though the sibling names help.

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% — both parameters have descriptions (accountId and locationId). The tool description itself adds no parameter details, but the baseline of 3 is appropriate because the schema already carries the semantic burden. The description does not clarify the purpose of locationId (e.g., that it defaults to GHL_LOCATION_ID), but the schema already states that.

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 'Get Twitter profile' uses a specific verb (Get) and a clear resource (Twitter profile). It is unambiguous about what it does, but it does not distinguish itself from sibling tools like social_media_posting_get_facebook_page_group or social_media_posting_get_tiktok_profile. The name and description are essentially redundant, but it is still clear and non-tautological.

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 provides no guidance on when to use this tool versus alternatives. With many sibling 'get_*_profile' tools for different platforms, there is no indication of the conditions that would lead an agent to choose this one. It does not mention prerequisites such as needing an attached Twitter account, nor does it note that other tools exist for other platforms.

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