Search Capacities objects

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds value by specifying exact search scope (title-only, no body/properties), return format (IDs and titles), and filtering behavior (optional structures). No contradictions.

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?

Three sentences, front-loaded with the tool's primary purpose, immediate constraints, and follow-up usage. No filler or redundancy.

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 tool's moderate complexity, rich schema with 100% coverage, complete annotations, and presence of an output schema, the description fully covers what the tool does, its constraints, and how its output is used. No gaps remain.

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 covers 100% of parameters with descriptions. The description adds no additional param semantics, but this is acceptable since schema coverage is high and the baseline is 3. Extra point for clarifying that apiToken must not be echoed or copied from content, which is security-critical guidance not in the schema.

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 clearly that it searches Capacities objects by title only, with optional filtering by structures. Distinguishes itself from siblings like get_object (single object retrieval) and list_objects (unfiltered listing) by specifying the search scope and constraints.

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?

Explicitly says when to use this (title-only search for objects) and what it does not search (body blocks or property values). Mentions that results include IDs and titles for use with get_object or relation fields. Could further clarify when to prefer siblings like list_objects or get_object.

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