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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the non-obvious cross-tool linkage of installation_id to fleet and room-booking operations, which is useful, but says nothing about return format, pagination, or limits.

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?

A single front-loaded summary sentence states the resource and scope, followed by a tight bulleted list pairing each action with its effect and parameters. Every line earns its place and the structure makes scanning for the right action trivial.

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 multi-action tool with annotations covering safety and no output schema, the description covers all four operations and their key parameter, plus the installation_id linkage. It stops short of describing what each list/get returns, which is the main remaining gap.

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 coverage is reported at 100%, but the params object is a generic untyped bag, so the description carries real weight by naming installation_id as the path parameter for both getFleet and listFleetDevices and by omitting it for the two list actions. This adds meaning beyond the schema's bare 'path, query and body parameters by name'.

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 states a clear resource (account apps and fleets) and enumerates each of the four operations with a specific verb+object: listApps, listAppInstallations, getFleet, listFleetDevices. An agent can tell exactly what each action does. It does not explicitly contrast with the AccountAppsWriteTool sibling, but the read/write split is apparent from the name and readOnlyHint.

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 implies usage by mapping each action to its effect, but it gives no explicit when-to-use or when-not guidance versus the Write sibling or other read tools. The one genuinely useful routing hint is that 'an installation's id is the installation_id the fleet and room booking operations take', which cross-links tools but is not a usage rule.

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