marketo_get_lead_by_email

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

With no annotations, the description carries full burden for behavioral disclosure. It fails to mention side effects, rate limits, permissions, or data freshness. Being a read operation is implied but not stated explicitly.

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 sentences clearly convey purpose and implementation detail. No fluff, front-loaded with the main action. Achieves maximal density for the given 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 no output schema, the description does not explain return format, pagination, or error cases. For a simple lookup, this may be adequate, but lacks completeness for an agent to fully anticipate behavior.

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?

Input schema has 100% description coverage, so baseline is 3. Description adds minimal value beyond schema by noting 'Uses filterType=email' but does not explain the meaning or constraints of the 'fields' parameter in any actionable way.

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 tool's purpose: 'Look up a lead by email address.' This is a specific verb-resource pair and distinguishes from sibling 'marketo_get_lead_by_id' which uses ID instead of email.

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 usage for email-based lookups but does not explicitly state when to use this tool over alternatives like 'marketo_get_lead_by_id' or 'marketo_create_or_update_leads'. No guidance on prerequisites or appropriate contexts is provided.

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