apex_list_auth_schemes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds minimal context about the app being existing, but does not disclose behavior like error handling or pagination. With annotations present, this is adequate but not rich.

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 sentence that puts the verb first, identifies the resource, and is free of extraneous words. Every word adds value, making it highly efficient and easy to parse.

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, read-only listing tool with one parameter, an output schema present, and comprehensive annotations, the description is sufficient. It clearly states what the tool does, and the structured data covers safety, parameters, and return types. No additional context is necessary for correct invocation.

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 fully covers the single parameter app_id with its description 'Application ID' (100% coverage). The tool description does not add any additional semantic meaning about the parameter beyond what the schema provides, so the score remains at the baseline of 3.

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 uses a specific verb 'List' and resource 'authorization schemes' with scope 'in an existing app', clearly distinguishing it from other listing tools like apex_list_apps or apex_list_pages. It is unambiguous and immediately conveys 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 phrase 'in an existing app' implies that the tool is intended for apps that already exist, but the description does not explicitly state when to use this tool relative to alternatives such as apex_add_auth_scheme or apex_get_app_details. There is no mention of exclusions or alternative tools, making the usage guidance merely implied.

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