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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and caching profile is fully covered. Beyond that the description only adds the identity semantics (integration_id or base_url), which is parameter-level rather than behavioral; there is no mention of pagination, result size, or behavior when the integration is unknown.

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 sentences, front-loaded with the action and return fields, followed by the routing guidance. Every clause earns its place with no redundancy.

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, fully-annotated list tool with complete parameter documentation, the description covers what it returns, how to identify the target, and when to call it. Minor gaps remain: it does not mention pagination or behavior for an unknown/invalid integration, and it doesn't route against the other integrations read tools.

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 100%, so the schema already documents base_url, in_workspace, and integration_id, including the 'Or the integration's base URL' either/or phrasing. The description's 'Identify it by integration_id or base_url' restates that without adding format or precedence details, so the baseline of 3 applies.

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?

States a specific verb and resource ('List every endpoint ... registered on an HTTP-API integration') and even enumerates the returned fields (operationId, method, path). It routes the agent away from the write siblings by naming integrations.remove_endpoints and integrations.add_endpoints, so it is distinguishable without opening a schema.

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?

Gives a concrete usage scenario ('Use this to review what tools exist before integrations.remove_endpoints or add_endpoints'), which implies the read-first workflow. It does not, however, distinguish itself from adjacent read siblings such as integrations_list, integrations_search_tools, or integrations_get_tool_schema, so an agent could still pick the wrong read tool.

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