syndicate_stats

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

Description implies read-only behavior by showing stats, but no explicit safety or side-effect declaration. Annotations are absent, so description carries full burden; lacks explicit statement of no side effects.

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?

Single sentence plus usage sentence. Every word adds value. Front-loaded with purpose, no redundancy.

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?

Lists all return categories (lessons, confirms, categories, trusted lessons, growth, contributors). No output schema, but description fully describes the output. Agent can act without guessing.

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?

No parameters in input schema, so description naturally provides no additional param info. Baseline of 4 is appropriate for zero-parameter tools.

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?

Description clearly states it shows health metrics of global Knowledge Commons, listing specific items. Verb 'show' is appropriate. Distinguishes from siblings like syndicate_search and syndicate_trending by focusing on aggregate stats. Includes usage context for weekly reviews.

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?

States to use for weekly reviews or exploring community knowledge. Provides clear context but does not explicitly exclude alternative tools or mention when not to use.

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