pipedrive_me

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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals the default identity binding (token owner) and the shared-token scenario, but says nothing about permissions required, failure behavior when as_user does not resolve, or rate limits.

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 short sentences, zero filler, with the identity default stated before the override option. Every clause earns its place.

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?

For a one-optional-param read tool with no output schema, the description covers the essential decision (default identity vs. impersonation) and the shared-token context. The remaining gaps, resolution failures and permissions, are minor.

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% and the single parameter is fully documented there, so the baseline is 3. The description's 'by name or email' restates the schema's accepted formats without adding syntax, matching rules, or error 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?

States a specific verb and resource ('Show the current Pipedrive user') plus the scope qualifier '(API token owner)', which cleanly separates it from the sibling user tools (pipedrive_users_get, pipedrive_users_list) that require an explicit identifier. An agent can pick this tool without opening the schema.

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?

Gives a positive routing rule: use as_user to resolve a different team member by name or email. It does not state a when-not-to-use case (e.g., use users_get when you already have an ID), but the implied default-vs-override decision is clear enough to act on.

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