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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add useful scope information by saying only metadata/approved fields are returned and that secrets, contacts and original files are excluded. It says nothing however about pagination, result ordering, or what 'authorised' means operationally.

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 resource in front and the exclusion list trailing, so nothing is buried. The phrase 'through the existing application' is slightly vague filler but the text is essentially waste-free.

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 read-only list tool with strong annotations and no output schema, the description covering authorization and return-field scope is nearly sufficient. The remaining gap is pagination/filtering behavior, which an agent would need to call this correctly with limit, offset and query.

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 all three parameters (limit, query, offset) are undocumented in both schema and description. The description provides no hint about what query filters on, how limit/offset interact, or what the pagination ceiling of 100 means in practice, so it does not compensate for the coverage gap.

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 gives a clear verb-plus-resource: it reads authorised OAuth app metadata. That distinguishes it from credential-oriented siblings such as list_api_key_metadata and list_webhook_metadata, though it never names those siblings explicitly to anchor the distinction.

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 use this tool instead of the many other list_* metadata tools, and no prerequisites or exclusions are given. The agent must infer usage from the tool name alone.

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