social

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The single word 'social' reveals nothing about whether this is a read or write operation, what permissions might be required, rate limits, side effects, or any behavioral characteristics. This is completely inadequate for a tool with zero annotation coverage.

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?

While 'social' is extremely brief, this represents under-specification rather than effective conciseness. A single word cannot convey the necessary information about a tool's purpose and behavior. The description fails to be appropriately sized for the complexity of the tool (which appears to be part of a large social media/data platform based on sibling names).

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 complexity implied by 70+ sibling tools in what appears to be a social media/data platform, and with no annotations, no output schema, and a completely inadequate description, this tool definition is severely incomplete. An AI agent would have no idea what this tool does or how to use it appropriately in context.

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 tool has zero parameters (schema coverage is 100% with no properties), so there are no parameters to document. The description doesn't need to explain any parameters, which meets the baseline expectation for a parameterless tool. No points are deducted for not discussing nonexistent parameters.

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?

Tautological: description restates name/title.

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 absolutely no guidance about when to use this tool, when not to use it, or what alternatives might exist. With 70+ sibling tools and no context about this tool's purpose, there's zero usage guidance for an AI agent.

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