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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuine data-boundary constraint ('no secrets, contacts or original files'), which is useful, but it says nothing about pagination behaviour, result size, or what 'authorised' means in auth terms.

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, front-loaded, with no filler or repetition. It is efficient, though efficiency is partly achieved by omitting needed content rather than by tight editing.

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 three undocumented parameters, no output schema, and no info about what fields are returned or how paging works, the description is far too thin. Its exclusions help, but an agent cannot predict results or paginate correctly from this.

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% and the description never mentions limit, query or offset. Since the schema gives bare types and bounds with no prose, the description was the only place to explain the query filter or pagination semantics, and it does not.

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 verb and resource are recognisable (read tenant settings metadata), but 'metadata' merely restates the tool name and the description never says what settings are actually covered. It offers no differentiation from close siblings such as get_tenant_capability_map, list_tenant_user_metadata or get_branding_metadata.

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 statement of when to call this tool versus the many other tenant-level read tools, and no prerequisites or exclusions beyond a vague 'authorised'. The agent is left to infer usage purely from the name.

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