openid_connect_user_info

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

No annotations provided; description only says 'get identity'. Does not disclose whether this is a read-only operation, authentication requirements, rate limits, or what fields are returned. Minimal behavioral info beyond the purpose.

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?

Single sentence, no filler. Efficiently conveys the core purpose without excess.

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?

Adequate for a simple parameterless tool with an output schema, but lacks context about when to call, how it relates to OAuth flow, and what 'identity' includes (e.g., user ID, email, etc.).

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?

No parameters defined, input schema is empty (coverage 100%). Description does not add parameter info, but there is nothing to explain. Baseline of 4 is appropriate given zero 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?

Clearly states it retrieves the identity of a user who authorized 'Sign in with Slack'. Verb+resource is specific and well defined, and it is distinct from sibling 'openid_connect_token' which deals with token exchange.

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 on when to use this tool versus alternatives like 'openid_connect_token' or other identity-related tools (e.g., 'users_info', 'users_identity'). Does not mention prerequisites (e.g., prior authorization) or context.

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