cor_get_user

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

No annotations provided. Description lacks details on authentication, rate limits, error cases (e.g., user not found), or side effects. For a read operation, basic safety is implied but not confirmed.

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 sentences, zero fluff. Purpose is stated upfront. No unnecessary context for a simple get operation.

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 only one parameter and existence of output schema, the description is minimal but sufficient for a straightforward retrieval. However, it could hint at typical use cases like fetching user details for display.

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?

Only one parameter with schema coverage 0%. The description adds a brief label 'The user ID' which marginally clarifies the parameter's purpose beyond its name, but does not specify format or constraints.

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 explicitly uses verb 'Get' and resource 'user' with qualifier 'by ID'. This clearly differentiates from sibling list tools like cor_list_users and other get-by-ID tools by specifying the identifier.

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 description implies usage for retrieving a single user by ID, but does not provide guidance on when to use this vs cor_list_users or other tools. No alternative mention or exclusion criteria.

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