github_users_delete_social_account_for_authenticated_user

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

The description implies a mutation but does not clarify whether it deletes all social accounts at once or one at a time. No details on reversibility, confirmation, or side effects. Since annotations are absent, the description should carry this burden but fails.

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, front-loaded sentence with no extraneous words. It is as concise as possible.

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 lack of parameters and annotations, the description should explicitly state what is deleted (all or specific) and any consequences. The plural 'accounts' vs singular in name creates ambiguity, reducing 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?

The input schema has no parameters, so description need not explain them. However, it does not clarify the meaning of 'social accounts' or the deletion scope beyond the name. Baseline 3 is appropriate.

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 action (delete), resource (social accounts), and scope (authenticated user). It directly matches the tool name and distinguishes from related tools like add or list.

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 or list social accounts). No context about prerequisites or behavior.

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