get_organization_fields

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

No annotations provided. The description explains the return type and example usage, but does not disclose behavioral traits such as authentication requirements, rate limits, or whether the response is paginated. Basic transparency, but not comprehensive.

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?

Description is relatively concise with a clear intro, return description, and example. Could be slightly more streamlined, but overall efficient.

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?

With no parameters and an output schema present, the description adequately covers the tool's purpose and return structure. Provides context that it is essential for custom fields, making it fairly 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?

The tool has 0 parameters, so baseline is 4. The description provides an example call 'get_organization_fields()' confirming no arguments are needed, which adds clarity beyond the empty 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 clearly states the tool retrieves all organization field definitions from Pipedrive, using the verb 'Get' and specifying the resource. It distinguishes from sibling tools like get_deal_fields and get_person_fields by focusing on 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?

The description implies usage for understanding custom fields in organization data, but does not explicitly state when to use this tool versus alternatives or provide any exclusions. No guidance on prerequisites or contextual when-to-use.

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