discover-fields

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

The verb 'List' signals a read-style operation, and there is no contradiction with annotations since no annotations are provided. Still, with no annotations, the description carries the full behavioral burden and does not disclose pagination, output format, or behavior for invalid dataset IDs.

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 one concise sentence with no filler. The key scope information appears up front, making it easy for an agent to quickly understand the tool's purpose.

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 single-parameter list tool, the description adequately states what is returned and the input scope. It is reasonably complete even without an output schema, though it does not mention how dataset IDs can be obtained or handle invalid inputs.

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 schema already describes datasetId as 'The dataset ID (alphanumeric, hyphens, underscores)' with 100% parameter coverage. The description adds only the word 'specific', which reinforces the scope but does not meaningfully supplement the schema's documentation.

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 states a clear operation and resource: 'List available fields for a specific BambooHR dataset'. It scopes the tool to a single dataset, which helps distinguish it from discover-datasets, but it does not explicitly differentiate it from all sibling tools like get-meta-fields or run-custom-report.

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 phrase 'for a specific BambooHR dataset' implies this tool is appropriate when a caller has a dataset ID and wants its fields. However, the description does not provide explicit guidance on when to prefer alternatives, mention prerequisite steps like discovering datasets first, or state when not to use this tool.

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