load_process_login

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

Annotations cover safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description still adds real behavioral context: the password is never a parameter, the result lists loaded names and never values, and secret handling requires a chmod 600 file outside the repo — genuine security-relevant disclosure beyond 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?

Five short sentences, front-loaded with the primary action and then the prerequisites. Dense but every sentence carries information; the telegraphic style is efficient rather than padded.

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?

An output schema exists, so return shape need not be spelled out, and the description nonetheless notes the result contains loaded names only. It covers the credential-file prerequisite, the no-argument password constraint, and the readiness_check follow-up, leaving little an agent needs missing for correct invocation.

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 0% and the single parameter (env_file) is undocumented in the schema, so the description must compensate — and it does, specifying exactly what the file must contain (ZEUS_USERNAME, ZEUS_PASSWORD), where it should live, and its required 600 permissions. This gives the agent enough to construct a valid argument.

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?

States a specific verb and resource: 'Load Zeus login from a mode-600 env file into this process.' It also distinguishes this from set_prereq ('stores presence flags only'), which is the closest sibling, and clarifies it does not take the password as an argument. Clear, though it does not fully map itself against the broader sibling set.

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 workflow sequencing: prepare the env file, pass its path, then call readiness_check. This tells the agent the context and downstream step. It stops short of stating when-not-to-use conditions, but the setup and follow-up guidance is concrete.

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