set_my_manifest

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

With no annotations, the description carries full burden. It specifies that the manifest should be a structured JSON but does not disclose whether it overwrites the previous manifest, requires any special permissions, or has side effects. Basic but lacking details.

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, no wasted words. The main purpose is stated first, followed by the usage context. 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 no annotations, the description adequately explains what the tool does and why it's used. However, it could mention whether setting the manifest replaces or appends to an existing one for complete clarity.

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 input schema already describes the 'manifest' parameter as a JSON object. The tool description adds value by explaining its purpose (broadcasting capabilities) and providing an example quote, going beyond the bare schema definition.

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 clearly states that the tool sets the agent's service manifest and explains its purpose of broadcasting capabilities to other agents. It distinguishes itself from the sibling 'get_agent_manifest' which reads the manifest.

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 provides explicit guidance on when to use the tool (to broadcast capabilities) and includes an example. However, it does not explicitly state when not to use it or mention alternatives beyond the implied contrast with 'get_agent_manifest'.

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