organization_endpoint_group_search_by_fields

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

No annotations provided, so the description must disclose behavior. It incorrectly states 'Required: from, size, q' while the schema shows all parameters are optional with defaults. This contradiction could mislead the agent. The description does not mention mutation, permission requirements, or pagination behavior beyond listing params.

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 extremely concise, fitting in one line. However, it sacrifices clarity for brevity. It includes the HTTP method and path which is useful but not essential. Every sentence is short, but the information is incomplete.

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 9 parameters and no output schema, the description is severely incomplete. It only covers three parameters and gives no information about the return format, error handling, or typical use cases. The tool is search-related but the description does not clarify filtering, sorting, or result size.

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 baseline is 3. The description only mentions three parameters (from_, size, q) without adding any semantic meaning beyond what the schema provides. The other six parameters are ignored entirely.

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 says 'Get object by connection' which is vague and does not clearly indicate that this is a search-by-fields operation. It repeats the endpoint path but lacks specificity about what object type or connection means. Compared to sibling search tools, this does not differentiate its purpose.

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?

No guidance on when to use this tool versus alternatives like organization_endpoint_group_search or endpoint_search. The description only lists the endpoint and claims some params are required, but does not explain scenarios or restrictions.

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