cme_creds

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

No annotations provided. The description mentions view/search/export but omits the 'clear' action from the schema, which is destructive. This incomplete disclosure leaves the agent unaware of behavioral traits.

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 concise with two sentences, front-loaded with the main purpose. However, the list of actions is incomplete compared to the schema.

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 tool with 3 parameters and no output schema, the description covers basic purpose but omits the destructive 'clear' action, making it partially incomplete.

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% but the description only lists three actions (view, search, export), missing 'clear' which is in the action parameter. This inconsistency adds confusion rather than clarity.

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 manages the NetExec credential database with verbs 'View, search, and export', distinguishing it from sibling tools focused on different protocols or actions.

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 management after scans but does not explicitly state when to use this tool versus alternatives like cme_spray or protocol-specific tools.

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