browse_collections

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states 'Browse,' implying a read-only operation, but does not explain output format, pagination, data freshness, or authentication requirements. Critical traits are omitted.

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 sentence with no waste. It is concise and to the point, but could include more information (e.g., output hint) without becoming verbose. The brevity does not harm comprehension but limits completeness.

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?

Given the simple schema (1 optional param), no output schema, and presence of related sibling tools, the description fails to explain what the output looks like (list of collections? providers? both?) or how it relates to search and metadata tools. An agent lacks sufficient context for correct invocation.

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 input schema covers the only parameter 'provider' with a clear description ('Filter by specific data provider'). The tool description does not add additional meaning beyond the schema, but since schema description coverage is 100%, a score of 3 is appropriate.

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 the action ('Browse'), the resource ('available collections and providers'), and the scope ('OpenArchives.gr'). It distinguishes itself from sibling tools like search_archives (search) and get_document_metadata (metadata), as browsing collections/providers is a distinct operation.

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?

No guidance on when to use this tool versus alternatives (e.g., when to browse vs search). The description does not mention any prerequisites, use cases, or exclusions. An agent would have no context to choose this tool over search_archives or get_document_types.

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