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

There are no annotations, so the description carries the full burden. It does disclose that the tool returns object summaries and supports pagination via limit/offset, which is useful. However, it omits details about read-only behavior, permissions, default sorting, or any edge cases, providing only basic behavioral transparency.

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 two concise sentences that are front-loaded with the verb and resource. The first sentence states purpose, the second covers filters/pagination and output behavior. Every clause earns its place with no redundant or filler text.

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 straightforward list tool with 6 optional parameters and no output schema, the description covers the key aspects: purpose, filter types, pagination, and return summary type. It could more explicitly distinguish from search_all, but the overall context is sufficiently complete.

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 baseline is 3. The description adds a bit of semantic grouping by mentioning filters (type, database, module, name substring) and pagination (limit/offset), but it largely repeats what the schema already documents, so it does not significantly enhance parameter understanding.

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?

Description uses specific verb 'browse and filter' and clearly identifies the resource as 'Ross ERP 8.0 objects' with an explicit list of object types. It distinguishes itself from lookup_table by stating that it returns summaries and directs users to lookup_table for full detail, making the purpose unmistakable.

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 explicit guidance to 'use lookup_table for full detail,' providing a clear alternative and implying this tool is for browsing/filtering summaries. It explains the filter and pagination capabilities, but it does not explicitly discuss when not to use it relative to other siblings like search_all or find_column, so it stops short of full when/when-not coverage.

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