geo_social_generate

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

Annotations are absent, so the description carries the full burden. It vaguely mentions 'mathematically aligned with market intent centroids' and 'RAG citation consensus', but does not disclose what the tool actually does beyond generating text, whether it modifies any state, requires permissions, has rate limits, or what the return format looks like. For a generation tool, this is a significant gap.

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?

A single sentence that is not excessively long but is dense with jargon ('market intent centroids', 'RAG citation consensus') that may obscure the intended meaning. The core action is front-loaded, but the added phrases provide little value to an agent unfamiliar with the domain. It is usable but not optimally clear.

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 no annotations and no output schema, the description alone must make the tool self-explanatory. It lacks guidance on when to use it relative to siblings, what inputs are expected to achieve, and what kind of output to expect. The jargon suggests a sophisticated workflow but leaves too much to inference for an agent to use it correctly without additional 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?

Schema description coverage is 100%, so the schema fully documents url, format, and seed_topic. The description adds no additional meaning or nuance to the parameters; it does not explain how 'url' feeds into generation or elaborate on 'seed_topic'. Baseline of 3 applies because the schema already covers all parameter documentation.

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?

States a specific verb ('Generate') and resource ('viral social publications') and enumerates the formats (LinkedIn, X/Threads, Debate, Carousel). The phrase 'mathematically aligned with market intent centroids to build external RAG citation consensus' hints at the underlying approach, though it is jargon-heavy. It is distinct from siblings geo_audit and agentic_scan but does not explicitly differentiate, so not a 5.

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?

Provides no guidance on when to use this tool versus siblings, no prerequisites, and no exclusions. The description describes what it does but not the context in which it should be invoked or how it relates to geo_audit or agentic_scan. An agent is left to infer appropriate usage from the purpose alone.

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