search_by_license

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

No annotations are provided, so the description carries full burden. It states it returns 'List of matching record summaries,' indicating a read operation, but does not explicitly declare it non-destructive or disclose any side effects, permissions, or pagination behavior beyond parameter defaults.

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 well-structured with a brief header followed by a parameter list in docstring format. It is concise and front-loaded, though the parameter section could be slightly more terse without losing 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?

Given the tool has 5 parameters (1 required) and an output schema exists, the description covers the essential information: purpose, parameter meanings, and return type. It lacks error scenarios or edge cases but is sufficient for basic use.

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 input schema has 0% description coverage, but the description provides clear documentation for all 5 parameters, including the required 'license' with examples, optional 'query', and defaults for 'sort', 'page', and 'size'. This adds significant value beyond the bare 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?

The description clearly states 'Find records under a specific license,' specifying the action (find) and resource (records) with a distinct filtering criterion (license). This differentiates it from sibling tools like 'search_records' (general search) and 'search_by_community'.

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 explicitly mentions the required 'license' parameter and provides examples, implying it should be used for license-based filtering. However, no guidance is given on when not to use this tool (e.g., for non-license queries) or explicit alternatives among siblings.

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