secret_create

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

Discloses write-once nature, that payload cannot be read back or changed, rotation method, and return metadata limitation. Adds value beyond annotations (readOnlyHint=false, destructiveHint=false) without contradiction.

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?

Structured with paragraphs and an args list; every sentence adds value. Slightly lengthy but justified by the complexity. Good front-loading of key information.

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?

Despite no output schema and minimal annotations, the description covers purpose, prerequisites, behavioral constraints, parameter details, return value, and alternatives. Complete for a secret creation tool.

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?

With 0% schema description coverage, the description fully compensates by explaining all four parameters: data (max 500KB, conditional empty), name (unique), labels, and driver (external store). Provides constraints and usage details.

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 the action 'Create a swarm secret' and adds context 'requires a swarm manager'. Distinguishes from sibling config_create for non-sensitive data, making it specific and differentiated.

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?

Explicitly states prerequisite ('requires a swarm manager') and provides an alternative for non-sensitive data using config_create. It lacks explicit when-to-use guidance, but the context is clear.

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