co_search_sentencias

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

Annotations already provide strong safety guarantees (readOnly, destructiveFalse, idempotent). The description adds minimal extra behavior (search over metadata), but does not mention pagination, result completeness, or query syntax beyond what's in the schema.

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?

Single sentence with no filler, front-loaded with verb and resource, every word earns its place.

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 rich annotations, output schema existence, and simple parameters, the description covers the essential purpose. Could mention query syntax features, but overall complete for a straightforward search tool.

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 coverage is 100% with descriptive parameter descriptions. The description does not add significant meaning beyond the schema, so baseline score 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?

The description uses specific verb 'search' with clear resource 'Corte Constitucional decision metadata', distinguishing it from sibling tool 'co_get_sentencia' which likely retrieves a single decision.

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?

The description implies usage for free-text queries against decision metadata. While it doesn't explicitly contrast with the sibling, the sibling's name suggests targeted retrieval, so the intended use is reasonably clear.

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