crm_get_pipeline_metadata

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

With no annotations and a description that is just a restatement of the name, the tool's behavioral characteristics are entirely undisclosed. There is no mention of read-only guarantees, permissions, rate limits, or what might be affected, which is a significant gap for a metadata-fetching tool.

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 but under-specifies the tool's function. A single sentence that merely echoes the tool name does not provide enough substance to be considered well-structured; it is more of a placeholder than a helpful description.

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?

Despite having no parameters, the description fails to explain what 'pipeline metadata' actually consists of, what the return value will contain, or how it relates to other CRM tools. The absence of an output schema and the vague description leaves the agent with insufficient information to confidently invoke 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 tool has zero parameters, so the input schema is trivially complete. The description adds no parameter-specific meaning, but since there are no parameters to document, the baseline of 4 is appropriate.

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 'Get pipeline metadata' is a tautology that simply restates the tool name without adding any detail about what 'pipeline metadata' entails. It lacks specificity about the content or scope of the metadata, and does not differentiate from sibling tools like crm_get_metadata_summary or crm_get_blueprint_metadata.

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 is provided about when to use this tool versus alternatives. The description offers no context on typical use cases, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.

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