dashclaw_secret_due

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

The description states it lists secrets due for rotation, which implies a read-only operation. However, it does not elaborate on what 'coming due' means precisely, nor does it describe the output format or any other behavioral traits. With no annotations provided, the description carries the full burden but is only moderately transparent.

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 extremely concise with two sentences that are front-loaded with the core action and usage guidance. Every sentence adds value without unnecessary detail.

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 list tool with two parameters and no output schema, the description covers the main points: what it does, when to call it, and a precaution. It could mention the return format or error conditions, but it is largely complete given the tool's simplicity.

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 description does not explain the 'agent_id' parameter, leaving its purpose ambiguous (only 50% schema coverage). It implicitly relates 'within_days' to the lookahead but adds no new meaning beyond the schema. The tool's description lacks sufficient parameter-level guidance.

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 it lists secrets due for rotation, using a specific verb and resource. It distinguishes from sibling tools like dashclaw_secret_list and dashclaw_secret_mark_rotated by focusing on upcoming rotations and adding the usage context.

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 gives clear guidance to call this before using credentials and to flag the operator if a credential appears in the result. It implies when to use the tool but does not explicitly name alternatives, though sibling tools provide context.

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