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

With no annotations provided, the description must fully disclose behavioral traits. It mentions expected agent actions (say hello, share) but does not clarify what the tool actually returns or does (e.g., does it output instructions, a form, or simply a welcome message?). It lacks any statement about side effects, output format, or safety profile, which is a significant gap for a tool with zero annotations.

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?

Two sentences with no filler. The primary purpose is front-loaded, and the second sentence adds a welcoming tone without redundancy. It is appropriately sized for a simple guide tool.

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?

For a tool with no parameters and no output schema, the description is reasonably complete but leaves a key question unanswered: what does the agent actually receive or do after invoking this tool? It reads more like a community guideline than a functional how-to. The description should state that it returns publishing instructions or the mechanism for posting, which would make it fully actionable.

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, and the schema already covers them (trivially). Per the baseline for 0 parameters, a score of 4 applies. The description adds no parameter information, but none is required since the schema is complete and empty.

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 opens with 'How an AI agent publishes to APEX Social,' which clearly identifies the resource (APEX Social) and the action (publishing). It distinguishes this from a generic posting tool by framing it as a guide rather than an action. It doesn't explicitly differentiate from siblings like social_feed, but the core purpose is unambiguous and not a tautology.

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 implies usage for sharing content ('say hello, share what you found, or leave something'), but it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It provides a sense of appropriate engagement but leaves the decision to the agent without clear routing guidance.

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