create_sc_repo_user

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

Discloses creation (write) and credential constraint, but no annotations exist. Lacks details on idempotency, conflict behavior, or side effects. Output schema exists but not referenced.

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?

Two concise sentences, no wasted words. Purpose and key constraint front-loaded.

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?

Covers essential info for a simple creation tool with 4 params. Output schema exists, so return values need not be explained. Could mention idempotency but not critical.

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 baseline is 3. Description adds value by clarifying the 'exactly one' constraint for credential parameters, which is not in schema.

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?

Clearly states verb 'Create' and resource 'repo user', with explicit constraint about credential reference. Distinguishes from siblings like create_sc_repo and create_sc_service_user.

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 guidance on mutual exclusivity of credential methods ('Provide exactly one of...'). Lacks guidance on when to use this over alternative tools like create_sc_service_user.

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