pipedrive_organizations_get

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

Description mentions 'resolved custom fields' indicating output behavior, but with no annotations, it fails to disclose other important traits like auth needs, rate limits, or that it's a read-only operation. Could be more transparent.

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?

Single sentence, front-loaded with verb and resource. Efficient, but could incorporate usage guidance without harming conciseness.

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 simple get tool with 3 parameters and no output schema, the description is adequate but lacks details on error scenarios, return format, and parameter usage. Slightly below complete.

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 only 33%, and the description adds no extra meaning to parameters beyond the schema's minimal descriptions. For example, 'include_fields' and 'custom_field_keys' are not explained.

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 tool retrieves a single organization by ID with full details including resolved custom fields. This distinguishes it from list/search tools that return multiple organizations.

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?

Usage is implied (use when you need full details of a specific organization by ID), but no explicit guidance on when not to use or comparison to sibling tools like pipedrive_organizations_search or pipedrive_organizations_list.

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