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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the file may be stale with unknown age unless exportedAt is supplied, only workbooks with inline/shared strings and no formulas or external XML entities are supported, and pod-wide file reads refuse application-restricted policies. These are real failure modes an agent needs before invoking.

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?

Five sentences, front-loaded with what the tool does and immediately followed by the negative scope ('creates no export'). Each remaining sentence adds a distinct constraint (staleness, workbook support, policy restriction) with no repetition.

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?

No output schema exists, so the description carries the return burden; 'Reads definition rows ... using its Rules and Sub Rules sheets' does indicate the shape (rows drawn from two sheets), which is adequate. Minor gap: it does not say what a row contains or how truncation at the limit is signalled.

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 entry, limit, fileName, connection and exportedAt are already documented. The description adds only oblique meaning ('using its Rules and Sub Rules sheets' explains why limit counts across both sheets, and 'age is unknown unless supplied' ties to exportedAt), so baseline 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 ('Reads definition rows from an existing Oracle valid-intersection ZIP or XLSX') and names the sheets read. It explicitly disclaims the adjacent capability ('It creates no export'), which separates it from export_data and the export_* siblings without requiring a schema comparison.

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 clear precondition: 'Use it after a separately confirmed export to inspect valid-intersection definitions,' which tells the agent this is an inspection step, not a generation step. It stops short of naming an explicit alternative tool or stating when not to use it.

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