Get value mappings

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the useful contextual trait that this is a listing operation supporting $top pagination, but discloses nothing else about behavior such as default page size, max results, or how skip/filter/select/orderby behave.

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?

Two short sentences with the main action front-loaded; there is no filler or repetition. The only minor structural flaw is that 'Supports listing and $top' awkwardly couples a behavior with a parameter, and the singular emphasis on $top is arbitrary given the other four parameters.

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 tool with five optional OData-style parameters and a direct sibling (search_value_mappings), the description is too thin. It does not help an agent decide between get and search, does not explain the filter/skip/select/orderby parameters, and given no output schema, offers no indication of what the response looks like.

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 0%, so the description carries the full burden for parameter meaning. It mentions only $top, leaving skip, filter, select, and orderby undocumented. The bare parameter names hint at OData-style semantics, but the description never says they are OData query options or explains their syntax.

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 a specific verb and resource ('Get all value mappings') and signals the operation type ('Supports listing'). This distinguishes it from search_value_mappings, since 'get all' implies a full listing versus a filtered search, though it never names the sibling explicitly.

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?

There is no guidance about when to use this tool versus search_value_mappings or get_message_mappings. The phrase 'Supports listing' weakly implies a paginated list use case, but no context, exclusions, or alternative-selection criteria are provided, leaving the agent to infer the choice.

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