searchPeopleByTag

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

No annotations are provided, so the description holds the full burden. It discloses the OR matching behavior and implies a read-only search, but does not mention authentication, rate limits, scoping, or return format. The behavior is adequately described for a simple search tool.

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?

Two sentences: first states purpose, second explains tag usage with an example. Every word earns its place, no 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?

No output schema exists, so the description should hint at return type. While 'find all people' implies a list of people objects, explicit mention of return format would improve completeness. However, for a simple search tool with three well-documented parameters, the description is sufficiently complete.

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%, but the description adds critical OR matching logic for the 'tags' parameter beyond the schema description. The limit and offset parameters are already well-described in the schema. Baseline is 3, with a 1-point bump for enriching tag semantics.

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 the specific verb 'find' and resource 'people with one or more tags', and clearly distinguishes from sibling tools like 'listPeople' (no tag filtering) and 'getPerson' (single person). The OR matching nuance is explicitly provided.

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?

Describes how to use tags (comma-separated for OR matching) and mentions default limit and pagination. However, it does not explicitly say when not to use this tool or suggest alternatives for AND matching or different filtering needs.

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