apex_add_auth_scheme

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

The description only restates the core action and adds no behavioral details beyond the annotations. No mention of side effects, permissions, idempotency, or whether it overwrites existing schemes, which is significant for a mutation tool.

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 a single, front-loaded sentence that directly states the purpose without unnecessary words. It is appropriately sized for the tool's simplicity and earns its place by conveying the core function.

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?

The tool has a fully detailed schema and an output schema, but the description lacks usage context and behavioral disclosure (e.g., whether it replaces existing schemes or requires admin rights). These gaps make it minimally viable for an agent to invoke correctly, though not richly complete.

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?

The schema description coverage is 100%, so the schema already explains all parameters in detail. The description adds minimal value beyond the schema, merely hinting at naming conventions in examples, which meets the baseline for schema-driven semantics.

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 a specific action ('Create') on a specific resource ('authorization scheme'), with concrete examples (IS_ADMIN, IS_MANAGER) that distinguish it from sibling list/view tools like apex_list_auth_schemes.

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?

No guidance is provided on when to use this tool vs. alternatives, nor when it should be avoided. There is no mention of prerequisites or comparison to other mutation tools, leaving the agent to infer usage solely from the schema.

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