Delimit Secret Get

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

The description discloses side effects beyond the annotations: it appends an access log entry via ai.secrets_broker.get_secret and does not return secrets to scopes unauthorized at store time. This is valuable behavioral context that the readOnlyHint=false and destructiveHint=false annotations alone do not provide, and it does not contradict them.

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?

The description is well-organized with clear sections: purpose, when to use, when not to use, sibling contrast, and side effects. Every sentence contributes actionable information, and the most important details are front-loaded.

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?

For a simple 3-parameter tool with an output schema present, the description is complete. It covers purpose, usage boundaries, side effects, and authorization scope, so an agent has enough context to invoke it correctly.

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 description coverage is 100%, so the input schema already documents all three parameters. The description adds the conceptual framing of just-in-time scope checking, but it does not add parameter-level meaning beyond what the schema provides. The baseline of 3 is appropriate here.

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 opens with a specific verb and resource: 'Request just-in-time access to a stored secret.' It also explicitly contrasts with delimit_secret_store and delimit_secret_access_log, so an agent can distinguish it from sibling tools without needing to inspect their schemas.

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 states exactly when to use the tool ('when a tool or agent needs a credential at execution time') and when NOT to use it, naming the alternatives: delimit_secret_store for adding secrets and delimit_secret_access_log for examining audit logs. This gives the agent explicit routing criteria.

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