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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to restate safety. It adds genuinely useful behavioral context: 'omitted fields are kept, null is refused', immediate visibility of setting changes on a published catalogue, and the list of what stays outside MCP scope (binary media, PDF replacements, API keys, REST webhooks, team, billing). These go well beyond 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 short and front-loaded: the first line gives the core purpose and the key configuring rule, followed by two compact scoping notes. No filler words; each clause earns its place, though the structure is slightly fragmented with the indented 'Setting changes...' and 'Binary media...' lines.

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 zero-parameter read-only discovery tool, the description is largely complete: it states what will be revealed, when to use it, and what is excluded from MCP control. It doesn't describe the return format, but with no output schema and minimal invocation requirements, that is a minor gap rather than a blocking one.

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 tool has zero parameters, so the schema supplies 100% of parameter information without the description needing to compensate. Baseline 4 is appropriate; there is no param semantic gap to fill.

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 title provides a clear verb and resource ('Discover the MCP settings, entitlements and schemas') and the description specifies the concrete contents ('Effective entitlements, JSON schemas and examples'). It stands apart from the many mutation and specific get/list siblings because it is framed as the read-before-configuring discovery tool, though the description itself lacks an explicit fetch/return verb.

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 gives an explicit usage trigger: 'Read before configuring'. This is clear context that the agent should call this before any update/set/publish operations. It does not explicitly name alternatives or exclusions relative to sibling tools, but the 'before configuring' framing sufficiently routes it.

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