manus_webhook_public_key

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

The description discloses that the tool returns a static public key suitable for caching, which is key behavioral info. Without annotations, it covers the main behavioral trait (no side effects, stable key). Could note return format but acceptable.

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 zero filler words. Every part serves a purpose: stating the action and providing a caching recommendation. Highly concise and well-structured.

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?

Given no output schema and zero parameters, the description covers the essential details. It could mention the key format or that it's stable, but the caching hint adds valuable completeness for a simple get operation.

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 schema coverage is 100% (trivially). The description adds no parameter info, but none is needed. Baseline for high coverage is 3, but with no params, a 4 is reasonable as there is no deficiency.

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 uses a specific verb 'Get' and resource 'RSA public key', clearly stating the tool's purpose. It distinguishes itself from sibling webhook tools (create, delete, events, list) which have different functions.

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 advises caching the key for 1 hour, providing practical usage guidance. While it does not explicitly state when to use vs alternatives, the clear purpose and sibling differentiation make usage context clear.

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