pipedrive_get_current_user

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety and side-effect profile. The description adds context about the response content (company and user details) but does not disclose additional behavioral traits such as authentication requirements or rate limits. With annotations handling most behavioral disclosure, a 3 is appropriate.

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, front-loaded with the primary purpose ('Identify the Pipedrive account this server is connected to') followed by the return details and use cases. There is no wasted wording, and it is efficiently structured.

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?

Since there is no output schema, the description should ideally specify the return structure. It mentions company name, id, domain, and user details, which gives a general idea, but does not provide exact field names or nesting. For a simple tool, this is adequate, but an agent may need to infer the location of the user ID. More specificity on field names would improve completeness.

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 tool has zero parameters, and the schema coverage is 100% (trivially). The description does not need to explain parameters, and the baseline for 0 parameters is 4. No additional parameter information is required.

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 the tool identifies the connected Pipedrive account and returns company details (name, id, domain) and the API key owner's user details. It is distinct from siblings like get_user and list_users, which target specific or all users, making the purpose unambiguous.

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?

It explicitly provides use cases: 'confirm which company the data is coming from, or to get your user ID.' This gives clear guidance on when to use it. It does not mention alternatives or exclusions, but given the tool's uniqueness, this is sufficient.

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