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

With no annotations, the description must carry the behavioral burden. It usefully discloses that facts come from source-backed records and the curated Change Watch, implying a read-only knowledge lookup. However, it does not explain what a result looks like or how missing/omitted version affects behavior, so transparency is adequate but not rich.

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?

The description is a single dense, information-rich sentence with an explicit optional-scoping instruction. It is reasonably front-loaded with the topic and contains no filler.

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 two-optional-parameter query the description covers subject, source, deadlines, and version scoping, which is enough structure to invoke it. Yet with no output schema, no annotations, and many sibling tools, it leaves the return shape, use cases, and selection boundaries to the agent.

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 both optional parameters. The description's 'Optionally scope to a version' reinforces the version parameter but adds no form, format, or default details beyond the schema; limit is not addressed.

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 a concrete subject ('Maximo / MAS support-lifecycle facts') and the specific data points: end-of-support, Extended Support transitions, and 2026/2027 deadlines. It is clear, but it lacks an explicit verb and does not distinguish itself from the conceptually similar sibling lifecycle_dates.

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 gives no when-to-use/when-not-to-use guidance and names no alternative tool, despite numerous siblings and a likely overlap with lifecycle_dates. 'Optionally scope to a version' is parameter usage, not selection guidance.

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