panelica_core_get_v1_search

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false; the description adds the required scope '*:*' and a read-only label, which is useful auth context. However, it does not disclose behavior such as result format, pagination, or which resources are searched.

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 only four short lines, front-loads the core label, and contains almost no wasted prose. 'Read-only' repeats an annotation, but the entry remains appropriately compact.

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 search endpoint with no output schema, the description should say what the search returns or which resource families it covers; neither is present. 'Quick search' plus a bare endpoint path is too thin for an agent to predict the response shape or match it to a user's search intent.

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 no parameters and the input schema is empty with 100% coverage, so the description has nothing parameter-related to explain. The baseline for a zero-parameter tool 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?

The description opens with 'Quick search', which merely restates the title and gives no resource or result scope. The endpoint path 'GET /v1/search' confirms it is a search operation but does not say what is being searched or how results are scoped.

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 is provided on when to use this search endpoint instead of other listed tools, and no alternative or exclusion is mentioned. The lines about Category, Required scopes, and Read-only describe access constraints, not usage conditions.

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