getAssigneeInfo

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention whether the tool is read-only, whether it requires the lead to exist, what happens if multiple parameters match different agents, or any side effects. The lack of such context leaves the agent underinformed.

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 a single sentence with no unnecessary words. It is concise, but could be improved by including more useful information without adding length.

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, the description should explain what the tool returns (e.g., agent ID, name, contact info). It also does not clarify if the parameters are mutually exclusive or combinable, nor does it mention error conditions. The description is incomplete for a lookup tool.

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%, and the description simply restates the parameter names in the context of lookup. It does not add meaning beyond what the schema already provides, such as explaining how parameters interact or giving examples.

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 action ('look up'), the resource ('assignee agent for a lead'), and the lookup criteria (phone, email, external ID). However, it does not distinguish this tool from similar siblings like getSalesAgentByLead or getMemberById, which could cause confusion.

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 the tool is used to find an assignee agent via contact information, but it provides no guidance on when to use this tool over alternatives, such as when to prefer one parameter over another, or when the tool is not appropriate.

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