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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description does add real side-effect context beyond the annotations: work is stored as context and peers are notified. However it omits what the notification entails, whether request_id drives idempotency, and any auth expectations.

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 short, front-loaded sentences with no filler. The brevity is efficient, though it tips into under-specification rather than true conciseness given the tool's complexity.

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 mutating, open-world, 4-parameter tool with no output schema and no parameter documentation, the description is far too thin. It never explains inputs, prerequisites, or the effect on the referenced project, leaving the agent without enough to invoke it correctly.

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 0% and the description mentions none of the four parameters. Nothing explains that request_id (minLength 8) is the idempotency/dedup key, what content's 120000-character bound means, or how project_id/agent_key scope the contribution, so the description fails to compensate for the coverage gap.

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 phrase 'Add private work' names a verb and a loosely defined resource, but 'private work' is opaque and doesn't map cleanly onto the schema fields (content, project_id) or distinguish this from siblings like speedbot_product_create, speedbot_product_publish, or speedbot_topic_post. An agent can infer this submits work into a product context, but only by guessing.

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?

There is no when-to-use, when-not-to-use, or alternative named anywhere. With ~20 product_* siblings and many other contribution-style tools (topic_post, exchange_post, collaborate), the description gives no routing signal for picking this tool over them.

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