octo_search_profiles

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

No annotations exist, so the description carries the burden. It does disclose the token requirement and the AND semantics for tags, but much of this repeats the parameter schema, and it does not state the relationship between search and tags when both are supplied. It also does not explicitly confirm the operation is read-only.

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 terse sentences with no filler; the main purpose leads, and the token requirement and tag behavior are compactly stated. Every sentence 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?

The schema covers all five parameters and an output schema exists, but the tool description leaves a key ambiguity: whether search and tags combine with AND or OR. It also does not mention how this search relates to the many listing and finding siblings, so an agent must infer the intended 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?

Schema coverage is 100%, so parameters are already documented in the input schema; the description adds no meaning beyond what the schema already provides for tags and title prefix. Baseline 3 is appropriate.

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 names a specific operation ('Search profiles') and defines the search criteria ('by title prefix or tags'), which distinguishes it from list/find siblings. It is clear but does not explicitly contrast it with octo_list_profiles or octo_find_profile_by_name.

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?

It provides a prerequisite ('Requires OCTO_API_TOKEN') and tag combination rule, but gives no guidance on when to choose this tool over octo_list_profiles or octo_find_profile_by_name. Without explicit alternatives or exclusions, an agent must infer usage from the tool name.

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