get_user

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

No annotations are provided, so the description carries the full burden. It states the operation is 'récupère' (retrieves), implying read-only, but does not explicitly mention side effects, authentication, or error behavior. The basic nature is clear, but depth is limited.

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 two sentences, but the second sentence is dense with provider-specific mapping details. All information is relevant and purposeful, though slightly lengthy for a simple getter.

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?

An output schema exists, so return values need not be described, but the description adds important context about provider types and page_id derivation. It does not cover error cases or permissions, but those are not essential given the schema and the tool's simplicity.

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 coverage is 0% and the description only repeats 'par son id' without explaining where the user_id comes from or adding constraints. The parameter is self-explanatory by title, but the description does not enrich its semantics.

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?

Description clearly states the verb 'récupère' (retrieves) and the resource 'informations d'un utilisateur' by id, and distinguishes the tool by mentioning connected providers and sub-accounts. It also ties the tool to a specific use case (before schedule_post), making its purpose unambiguous relative to sibling tools.

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?

Explicitly says to use this tool before schedule_post to identify the correct page_id, and provides concrete mapping rules for different provider types. This gives clear guidance on when to use the tool versus alternatives.

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