probely_create_credential

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 discloses that the tool creates a credential, returns an id and uri, and that the URI can be used for linking. However, it omits details like whether duplicate names cause errors, required permissions, or rate limits, leaving gaps for a first-time agent.

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 four short sentences, no fluff, and front-loaded with the primary purpose. Every sentence adds distinct value: creation action, sensitive flag tip, return structure, and linking usage.

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?

Given the complexity (5 parameters, no schema descriptions, no annotations), the description explains the return value and a key usage pattern but does not cover all input parameters or error cases. The presence of an output schema reduces the need to explain return values, but input semantics remain 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 0%, so the description must add meaning for 5 parameters. It only addresses is_sensitive ('Use is_sensitive=True for passwords') and implies value is for 'secure storage,' but ignores name, description, and team. This is insufficient for an agent to correctly populate all parameters.

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 'Create a credential for secure storage,' using a specific verb and resource. It distinguishes from siblings like probely_update_credential, probely_get_credential, and probely_list_credentials, leaving no ambiguity about the tool's function.

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 explicit usage guidance: 'Use is_sensitive=True for passwords' and explains how to link the credential to a sequence via the URI. While it lacks explicit when-not-to-use or alternatives, the context is clear for typical credential creation scenarios.

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