patch_package_search_by_fields

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

No annotations provided. The description contradicts the schema by declaring 'from', 'size', 'q' as required while the schema shows them as optional. No mention of authentication, rate limits, or return type.

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?

Extremely brief but misleading due to the required field contradiction. The description lacks logical structure and clarity.

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, no explanation of return values or pagination. For a search tool, this is inadequate.

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?

Only three parameters are mentioned, and they are mischaracterized as required. The description adds no meaningful context beyond the schema's parameter descriptions, which already exist.

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 states 'Get object by connection' which is vague; it likely means search by fields to retrieve objects. It also mentions 'Required: from, size, q' but these fields are optional in the schema, causing confusion.

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 vs alternatives. Sibling tools include many similar search_by_fields tools, but the description does not differentiate or specify context.

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