Lista Definições de campos personalizados (OData /CustomFieldsDefinitions). Filtre com $filter/$top/$skip/$orderby/$expand.
| Name | Required | Description | Default |
|---|---|---|---|
| $top | No | ||
| $skip | No | ||
| query | No | ||
| $count | No | ||
| $expand | No | ||
| $filter | No | ||
| $select | No | ||
| $orderby | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds no additional side effects or restrictions, but does not contradict the annotations.
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 a single concise sentence that directly states the purpose and available filters without unnecessary words.
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?
Provides the endpoint and filter hints, but does not describe the return structure or any potential limitations. For a simple list operation this is acceptable, though more detail could 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?
The schema has no parameter descriptions. The description enumerates some OData parameters but omits $count and $select, and does not explain their meanings beyond indicating they are for filtering.
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?
Clearly states it lists custom field definitions, specifying the OData endpoint. This distinguishes it from other list tools for different entities.
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?
Mentions OData filter options but does not explicitly state when to use this tool versus alternatives. However, the entity-specific name implies when it is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.