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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond the document-type examples; it does not mention that pagination is automatic or that an unbounded list may be returned.

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 zero filler; the resource and its contents are front-loaded, followed by the filtering modes.

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?

With a fully documented schema and complete annotations and no output schema to explain, the definition is nearly sufficient for calling the tool. It falls short only in not disambiguating from the closely named infrastructure-asset-document sibling.

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 every parameter is already documented in the schema. The description only restates the asset_id and category filters and says nothing about search, page, or per_page behavior. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (List) and resource (asset documents) and gives concrete examples of document content (O&M manuals, warranties, specs). It does not, however, distinguish itself from the near-identical sibling list_infrastructure_asset_documents or from get_asset_document, so sibling differentiation is missing.

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 clause 'Filter by asset_id or category' implies the two main retrieval modes, but there is no explicit when-to-use guidance, no mention of when to prefer get_asset_document, and no note that it returns all documents when unfiltered (all params optional).

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