github_users_add_social_account_for_authenticated_user

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

No annotations are provided, so the description must convey behavioral traits. It only says 'Add', implying a mutation, but does not disclose whether the operation is idempotent, reversible, or requires any authentication. Critical details like potential side effects or constraints are missing.

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 sentence (7 words), which is concise. However, it is too brief and omits important information. It is not verbose, but could be improved by adding more structure without sacrificing conciseness.

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 has 1 complex parameter, no annotations, and no output schema, the description is grossly insufficient. It does not explain how to structure the request body, what the response looks like, or error conditions. The agent cannot invoke this tool correctly based solely on the description.

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?

The input schema has one parameter 'body' with minimal description 'Request body (JSON object)'. The tool description adds no additional meaning about what fields the body should contain (e.g., account URL, platform type). While schema coverage is 100%, the description fails to compensate for the lack of detail in the schema.

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 'Add social accounts for the authenticated user' which clearly indicates the action (add) and resource (social accounts). However, it does not specify what constitutes a social account (e.g., platform URL or account name), making it somewhat vague. It is distinguishable from siblings like delete_social_account by the verb, but lacks specificity.

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 guidance is provided on when to use this tool versus alternatives (e.g., add_email, other user management tools). There is no mention of prerequisites, such as authentication status or required permissions. The description gives no usage context.

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