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

With no annotations, the description bears the full burden of behavioral disclosure. It states leads are 'Anonymized,' which is a behavior, but it doesn't disclose whether the operation is read-only, what the return format is, whether it consumes credits, or any side effects. The description is far too sparse to convey the behavioral profile adequately.

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 fragment, which is concise but not structured. Key information about the parameter and usage is missing. It under-specifies rather than being efficiently concise, so it fails the conciseness test.

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 the tool has one required parameter, no output schema, and no annotations, the description should clarify everything the agent needs. It explains neither the parameter nor the output, and offers no context about the 'presentations' or 'CTA forms' in relation to the ID. This is completely inadequate for correct invocation.

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 description coverage is 0%, so the description must explain the 'id' parameter, but it provides no mention of it. The description adds zero meaning about what 'id' refers to or how it should be used. This is a critical gap.

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 'Anonymized lead list from CTA forms in presentations' indicates the tool returns leads from presentation CTAs, but it's a noun phrase rather than an explicit verb statement. The title clarifies it lists leads, but the description itself is vague about scope and doesn't distinguish from sibling tools like crm_list_leads. Purpose is partially clear but lacks specific action and context.

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 usage guidance is provided. The description doesn't mention when to use this tool over siblings like crm_list_leads or list_agent_presentations, nor any prerequisites or context. An agent has no way to know the appropriate scenario for this tool.

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