input_secret

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

Describes key behavioral trait: value never passes through model or chat, goes directly to encrypted store. No annotations provided, so description carries full burden. Could mention whether it overwrites existing secrets or returns anything.

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, front-loaded with purpose. Every sentence adds essential information. No waste.

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?

No output schema, but description gives sufficient context for a simple interaction tool. Could clarify that dialog blocks execution, but overall complete.

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 coverage is 100%, baseline 3. Description adds value by noting name must be whitelisted in secrets.yml, which is not in schema. Also explains prompt parameter context.

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 it prompts user for a secret via macOS dialog and stores it, using specific verb 'Prompt' and resource 'secret'. Distinguishes from siblings like get_secret, set_secret by emphasizing user interaction.

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?

Provides explicit usage guidance: 'Use this when you need a token, password, or API key the user has not yet stored.' Also mentions prerequisite (name whitelisted). Could add explicit when-not-to-use, but inferred.

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