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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is supplied structurally. The description adds one piece of behavioral context — that the app must be connected for these actions to be relevant — but says nothing about pagination, since a 'limit' param with default 30 exists, nor whether results are live or cached.

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?

It is a single short sentence with no padding, which is good. But the wording is fragmentary and the trailing clause 'its actions' merely restates the head of the sentence rather than adding information, so brevity comes at the cost of clarity.

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 three-parameter, open-world lookup tool with no output schema, the description should explain what a returned 'tool' looks like (name, slug, description) and how paging works. Neither is covered, and the missing param semantics leave an agent guessing about limit and search behavior.

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 only 33%: toolkit is documented in the schema, while limit and search have no descriptions anywhere. The description adds nothing — it does not explain that results can be paged, that limit caps at 100, or that search filters actions by name — so it fails to 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 identifies the resource precisely: the set of actions ('tools') available for a single third-party app. However, it never states the verb 'list' or 'returns' — the retrieval semantics come from the tool name and title rather than the description, and it does not name sibling search_connectable_apps as the differentiator.

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 phrase 'once it is connected' hints at a prerequisite state, but the description gives no explicit when-to-use, when-not-to-use, or alternative guidance. The critical fact that the toolkit slug comes from search_connectable_apps appears only in the schema, not in the description.

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