ise_catalog_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description indicates this is a read-only operation ('Show cached catalog provenance'), which is good. However, it doesn't disclose what happens if no catalog is cached (error vs empty output), whether it triggers any refresh, or the format of the output. The word 'cached' is useful, implying no network call. But for a zero-parameter info tool, the behavioral disclosure is modest.

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, dense sentence that conveys complete information with zero wasted words. It lists exactly the four data points the tool returns (version, source URLs, generation time, per-surface entry counts) in an efficient, front-loaded manner. No redundancy, 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 zero-parameter info tool with no output schema, the description gives a thorough preview of the return contents (four distinct data categories). The tool is conceptually simple (show provenance metadata), so the description covers the key expectations. It could note whether the tool requires a deployment to be set/selected, but given the simplicity of the tool, this is a minor 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?

The tool has 0 parameters with 100% schema description coverage (trivially, since there are no parameters). Per the rubric, 0 params = baseline 4. The description adds meaningful context about what information the tool returns (version, URLs, generation time, entry counts), which helps the agent understand what output to expect even without an output schema.

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 clearly states what the tool does: 'Show cached catalog provenance' with specific details (target ISE version, source URLs, generation time, per-surface entry counts). This is a strong verb+resource pair that clearly differentiates it from siblings like ise_catalog_diff (which compares catalogs) and ise_ers_resources (which lists ERS resources). The term 'catalog' plus 'provenance' makes the purpose unambiguous and distinct.

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 effectively communicates when to use this tool: when you need to inspect cached catalog provenance metadata. It implies use for debugging catalog state, version checking, and audit. However, it doesn't explicitly state when NOT to use it or name alternatives (e.g., 'use ise_catalog_diff to compare versions'), though the sibling context makes the distinctions relatively clear. No exclusions are stated.

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