Show Custom Field Definition

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description adds little beyond stating it returns a JSON object. It does not disclose pagination behavior or other traits beyond what is implicit from the parameters.

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 concise at five sentences, each providing relevant information: purpose, usage, return type, required parameters, and API source. It is front-loaded with the main action but could be slightly more compact.

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?

While the schema covers parameters and annotations cover behavior, the description does not explain the return structure beyond 'JSON object describing the requested...' and omits pagination details despite page/per_page parameters. Given no output schema, more context on response content 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?

Schema description coverage is 100%, so the description adds no new parameter meaning beyond stating required parameters (id and company_id), which are already in the schema's required array. Baseline score of 3 applies.

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 verb ('returns') and resource ('Custom Field Definition'), distinguishing it from sibling tools by specifying the exact entity. It mentions fetching full details by identifier, which is specific and 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?

The description provides minimal usage guidance: it lists required parameters and the API endpoint, but does not explicitly state when to use this tool versus alternatives (e.g., list_custom_field_definitions or show_custom_field_lov_entry). No exclusions or preferred contexts are mentioned.

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