entitlements_get

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds 'Returns entitlement shape,' which is redundant given the output schema and does not provide additional behavioral context such as error behavior or permission requirements. No contradiction with 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 extremely concise with two short lines, immediately gives the purpose, and avoids filler. Every word earns its place.

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?

This is a simple getter with two fully documented parameters, an output schema, and annotations covering safety and idempotency. The description is adequate for the low complexity, though it could slightly benefit from an explicit usage pointer to sibling tools. Overall, it is complete enough for an agent to invoke correctly.

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 coverage is 100%—both application_id and entitlement_id have descriptive text with patterns. The description adds no extra parameter-level meaning, so it relies fully on the schema, matching the baseline of 3.

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 explicitly states 'Fetch a single entitlement'—a specific verb and resource, and the word 'single' clearly differentiates it from sibling tools like entitlements_list or entitlements_consume. It is unambiguous and front-loaded.

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 usage for retrieving one entitlement by ID but does not explicitly name alternatives or when-not-to-use. It contrasts with 'single' vs. list but never mentions entitlements_list or other sibling tools, leaving the guidance implicit.

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