delimit_secret_get

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

With no annotations, description carries full burden. It discloses side effect (appends access log entry) and behavioral constraint (does not return secrets to unauthorized scopes). Could mention failure modes, but transparent enough.

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?

Concise and front-loaded with main action. Each sentence adds value (when-to-use, sibling contrast, side effects). Could combine some sentences, but overall efficient.

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?

Covers usage context, side effects, and authorization constraints. Does not describe return structure, but output schema exists. Could mention error scenarios (e.g., missing secret), but still fairly 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?

Input schema has 100% coverage with descriptions. The description does not add extra meaning beyond what schema already provides (e.g., required status, broker scope check). Baseline 3 applies.

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 the tool's purpose: 'Request just-in-time access to a stored secret.' It uses specific verb 'request' and resource 'stored secret', and distinguishes itself from siblings (delimit_secret_store writes, delimit_secret_access_log shows audit trail).

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 provides 'When to use' (credential needs at execution time) and 'When NOT to use' (to add a secret or examine audit log), with direct references to alternate tools. Also includes sibling contrast.

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