social_media_posting_attach_twitter_profile

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

Annotations indicate readOnlyHint=false (mutation), openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds nothing beyond these hints—it does not explain the mutation's effects, required authentication, whether existing profile associations are overwritten, or what happens on the Twitter side. Since annotations are minimal, the description carries the burden of behavioral disclosure, and it fails entirely.

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 a single short sentence with no wasted words, but it is so under-specified that it does not serve its purpose. While conciseness itself is fine, the content is insufficient to guide an agent. It is not 'appropriately sized' because it omits essential 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?

With 9 parameters, no output schema, and no nested objects, the tool's context is not simple. The description provides no information about what the tool does beyond the verb 'attach', what the attached profile represents, how it relates to the account/company/location, or what a successful call returns. It is completely inadequate for an agent to call correctly.

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 only 33% (only accountId, companyId, locationId have descriptions). The description does not explain any of the 9 parameters (name, avatar, originId, username, verified, protected, etc.), nor does it clarify the purpose of the required accountId. With low schema coverage, the description should compensate, but it provides no parameter semantics at all.

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 states a verb ('attach') and a resource ('Twitter profile'), but it adds almost no information beyond what the tool's name already conveys. It does not specify what 'attach' means in this context, which fields are relevant, or how it differs from sibling attach tools like social_media_posting_attach_facebook_page_group. It is nearly a tautology of the tool name.

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?

There is no guidance on when to use this tool versus the similarly named sibling attach tools (e.g., attach_instagram_page_group, attach_linkedin_page_profile). No context is given about prerequisites, expected input sources, or scenarios where this tool is appropriate. The description provides zero usage direction.

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