get_organization

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

The description mentions it retrieves 'comprehensive information' and 'including all custom fields', but does not explicitly state it is a read-only operation or disclose any side effects. No annotations provided, so the description carries the burden but only partially addresses behavioral context.

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 succinct with a clear structure: purpose, arguments, returns, and example. Every sentence serves a purpose without redundancy.

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 the tool has a single parameter, an output schema (implied), and is a simple retrieval, the description covers all necessary aspects: what it does, what input is needed, and what is returned. No significant gaps.

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 to the 'org_id' parameter by stating 'The Pipedrive organization ID' and providing a concrete example, which is valuable given the schema has zero description coverage. It clarifies the parameter's purpose beyond the raw schema.

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 explicitly states 'Get a single organization by ID', clearly identifying the verb and resource. It distinguishes itself from sibling tools like 'get_organizations' (plural) and 'search_organizations' by focusing on a single entity retrieval.

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 provides a parameter description and a usage example, but does not specify when to use this tool versus alternatives (e.g., when to use 'get_organizations' for listing or 'search_organizations' for filtering). No guidance on when not to use it.

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