ninja_query_custom_fields

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

No annotations are provided, and the description only adds the scope of 'across all devices and organizations'. It does not disclose behavioral traits such as pagination behavior, performance implications, rate limits, or authentication requirements beyond what is evident from the tool name.

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 extremely concise, consisting of a single sentence with no wordiness. However, it could be slightly more informative without losing conciseness, e.g., mentioning pagination or filter capabilities.

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 7 parameters and no output schema or annotations, the description is too sparse. It does not explain return format, pagination cursors, or how to effectively use the parameters (e.g., updatedAfter, scopes), leaving the agent underinformed.

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 input schema has 100% description coverage, so the schema already documents each parameter. The description adds no additional meaning or context for the parameters beyond what the schema provides.

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 uses the verb 'Query' with the resource 'custom field values' and specifies the scope 'across all devices and organizations', clearly distinguishing it from sibling tools like ninja_get_device_custom_fields and ninja_get_organization_custom_fields.

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 the tool is for querying across all entities, but it does not explicitly state when to use this tool versus alternatives (e.g., for specific device/org queries) or provide any usage conditions or exclusions.

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