find_credential_access

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

No annotations are provided, so the description carries the full burden. It does not disclose whether this tool is read-only, destructive, requires authentication, or what side effects exist. The description only lists technique types without behavioral context.

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?

A single sentence listing examples is concise and front-loaded. However, it could be more structured with separate lines for clarity, but no waste.

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?

Lacks explanation of return values, prerequisites (e.g., environment_id from enumerate_host), and does not specify behavior for each credential_type. With many sibling tools, more differentiation is needed.

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 covers all three parameters (100%), so baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions, which already state the parameter names and defaults.

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 states 'Find credential access techniques' with specific examples like 'file harvesting, memory dumps, keychain access', clearly identifying the verb and resource. It distinguishes from sibling tools like 'find_token_abuse' which focuses on token theft specifically.

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 implies usage for credential access techniques but provides no explicit guidance on when to use this tool versus alternatives like 'find_token_abuse' or 'find_collection'. No exclusions or context are given.

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