get_person_object

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

No annotations are provided, so the description must fully disclose behavior. It states the tool uses Breeze Intelligence but does not specify if it's read-only, requires permissions, or has side effects. The output is not described, and there is no indication of data usage or privacy implications.

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, which is concise but lacks substantive detail. It front-loads the purpose but sacrifices completeness for brevity. It could be improved with more focused information.

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 that it is a data enrichment tool with no output schema and two parameters, the description is incomplete. It does not explain what kind of enriched data is returned, how Breeze Intelligence works, or any prerequisites. This leaves the agent without enough context to fully leverage the 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?

The input schema has 100% description coverage for its two parameters (email and output_variable_name). The description does not add any additional meaning beyond what the schema already provides, so it meets the baseline with no added value.

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 it gathers enriched user data using Breeze Intelligence, which provides a specific verb, resource, and source. However, it does not differentiate from sibling tools like enrich_person or contact_research that may also enrich person data, leaving ambiguity about when to use this tool.

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 offers no guidance on when to use this tool versus alternatives. It mentions 'deeper analysis' but does not explain criteria for selection, nor does it exclude other tools like enrich_person. The sibling list includes many similar tools, making this gap significant.

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