Perfil de una persona (por id)

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

No annotations are provided, so the description must cover behavioral traits. It mentions batch capability and auto-course lookup, but does not state whether the operation is read-only, safe, or if any destructive side effects exist. It is adequate but could be more explicit.

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 paragraph that is front-loaded with the most important information (profile fields, auto-course, batch). It is concise with no redundant text, though it could be slightly more structured with bullet points for clarity.

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 no output schema, the description covers the key return fields and the auto-course behavior. It is mostly complete for a profile retrieval tool, though it lacks details on error handling or authentication requirements.

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 description adds meaning beyond the schema: it explains the batch use for userId arrays with a max of 50, and clarifies that courseId is optional with an automatic fallback. This compensates for the schema's 50% description coverage.

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 that the tool gets a user profile by userId, including specific fields like name, email, role, time zone, and courses. It distinguishes from siblings by specifying details not covered in other tools like 'dutic_find_person' or 'dutic_list_participants'.

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 explains the automatic course discovery feature when courseId is omitted, which guides usage. However, it does not explicitly mention when not to use this tool or compare it to alternatives like 'dutic_find_person'.

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