search_behance_profiles

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 the tool searches and returns specific fields, implying a read-only operation. However, it does not disclose behavioral traits such as authentication requirements, rate limits, pagination behavior, or any side effects.

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 consists of two concise sentences. The first sentence states the purpose, and the second lists return fields. It is front-loaded and contains no unnecessary words.

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 no output schema and two parameters, the description covers purpose and return fields. However, it lacks details on pagination, ordering, and response structure, which are important for a search tool. The presence of sibling tools provides context but does not substitute for missing operational details.

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 both parameters described. The description adds examples for the keyword parameter (e.g., 'designer') but does not significantly enhance understanding beyond the schema. The maxItems parameter is not elaborated beyond schema defaults.

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 the verb 'Search' and the resource 'user profiles on Behance by keyword'. It distinguishes this tool from siblings by specifying it returns user profile fields like username, display name, etc., while siblings like search_behance_projects and search_behance_images target different resources.

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 use for keyword-based profile search but does not explicitly contrast with other search tools (e.g., search_behance_projects, search_behance_images) or specify when not to use this tool. It lacks usage context like prerequisites or when to prefer this over get_behance_profile_details.

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