identity_get_access_token_pkce_flow

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower, yet the description adds substantial operational context: Basic Base64(client_id:client_secret) in the auth header, application/x-www-form-urlencoded body required, and default-organization behavior when org id is omitted. The main flaw is that it is truncated mid-sentence ('Upon client_credentials…'), leaving the client_credentials and client_delegate behaviors unexplained.

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 deprecation notice is usefully front-loaded, but the text then repeats the same sentence (grant types listed twice), restates the endpoint, and ends abruptly with an ellipsis. The duplication and truncation waste space without adding information.

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 a nested body schema with full coverage and no output schema, the description supplies the key missing pieces (auth header, content type, org defaults, deprecation). But the truncation means grant types present in the schema (client_delegate/subject_token) go unaddressed in the description, so the picture is 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 description coverage is 100%, so the schema fully documents each body field and the baseline is 3. The description reinforces grant-type-specific org behavior but adds little that is not already in the per-field schema descriptions.

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?

It states a specific action (exchanging an authorization_code or refresh_token grant for an access token) and names the endpoint, so the core purpose is discernible. However, the tool name says 'pkce_flow' while the description describes only two grant types and a deprecation, and it does not distinguish itself from close siblings like identity_get_access_token_with_refresh_token or identity_get_access_token_with_authorization_request. That leaves an agent unsure which token-exchange tool to pick.

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 '[DEPRECATED]' marker and the explicit pointer to /oidc/oauth2/token give a real when-not-to-use signal, which is valuable. But the recommended alternative is a raw URL endpoint rather than a sibling tool, and there is no guidance on when to prefer this over the several identity_get_access_token_* siblings in the list.

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