dspace_search

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. It identifies a search operation but does not state read-only safety, authentication requirements, pagination behavior, rate limits, or result format; the schema supplies parameter details but not behavioral guarantees.

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?

Two tight sentences, front-loaded with the purpose followed by supported capabilities. There is no filler, and every sentence contributes to a quick understanding of the tool.

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 7-parameter search tool with no annotations, no output schema, and many sibling tools, the description omits when to use this versus list/get tools and provides no behavioral or authentication context. The rich schema helps with invocation mechanics but not selection.

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%, with all 7 parameters already documented in detail (Solr/Lucene syntax, UUID scope, enum type, filter key-value examples). The description restates parameter categories without adding syntax, defaults, or examples beyond the schema, so the baseline of 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 ('Search') and resource (DSpace items, communities, collections), making the core action clear. However, it does not explicitly differentiate this tool from sibling list/get tools such as dspace_list_communities or dspace_get_item, so an agent must infer when search is preferred.

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 explicit when-to-use or when-not-to-use guidance is provided. The description lists capabilities (full-text queries, type filtering, scoping, advanced filters) but never names alternatives or the conditions under which this tool should be chosen over sibling list/get tools.

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