Set app login

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

Beyond the annotations, the description discloses that credentials are stored with the deploy on the machine, visible only on a Cloudflare Access-protected catalog page, and that clearing is possible. It also warns against echoing secrets, which is safety-relevant. This adds meaningful behavioral context without contradicting the annotations.

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 compact and front-loaded: purpose first, storage/access context second, usage and security guidance third. Every sentence contributes, but the `creds=null` phrasing unnecessarily introduces ambiguity, preventing a top score.

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?

The description covers the core purpose, storage location, access restrictions, and a security instruction, which is strong for a write tool. However, the clearing mechanism is described via a parameter that does not exist in the schema, and there is no clarification of what the tool returns. This leaves an important operational gap for an agent.

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%, so the schema already documents every parameter. The description does not meaningfully add to parameter semantics and actively introduces a non-existent `creds` parameter for clearing, while the schema defines a `clear` boolean. This is misleading and could cause an agent to attempt an invalid call.

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 records app-specific login information for a deploy and explicitly distinguishes it from cloudfact's credentials. The verb 'Record' plus the resource ('how to get into the app behind a deploy') makes the purpose unambiguous and differentiates it from sibling tools.

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 useful context about where credentials are stored and shown, and it includes a critical safety instruction: 'Never put the user's secrets in your reply.' It also excludes cloudfact credentials. However, it does not name an alternative tool or provide a full when-not-to-use set, and the clearing instruction 'Pass creds=null to clear' is ambiguous because no `creds` parameter exists.

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