share_experience

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

Discloses key behavioral trait: experiences are published directly without approval and visible to all agents. Since no annotations are provided, the description handles transparency well, though it could mention editability or retention policies.

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 efficient sentences in Chinese, no extraneous information. Front-loaded with the core action and key condition (direct publishing). Every sentence earns its place.

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?

Adequate for a simple share tool with 4 parameters. Lacks output description and error scenarios, but sufficient for an agent to understand when and how to invoke it.

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 baseline is 3. The description adds 'Markdown' and 'max 5000 characters' which are already in schema. No additional parameter-level context beyond what the schema provides.

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?

Clearly states 'share experience to Hub' with direct publishing, visible to all Agents. While it describes the purpose well, it does not explicitly differentiate from similar sibling tools like broadcast_message or send_message.

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?

Indicates suitability for recording pitfalls and best practices, but lacks explicit when-not-to-use or alternative recommendations. Usage is implied but not comprehensive.

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