List projects

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

Annotations provide readOnlyHint=true. Description adds context by stating 'returns each project id, name, plan, and basic metadata' and explains the effect of include parameter. No contradictions. Good addition over annotations.

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: first states purpose and return content, second explains optional parameter use case. No wasted words. Information is front-loaded and easy to parse.

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?

Tool is simple with one optional param and output schema present. Description covers purpose, return fields, optional param usage, and provides context for when to use it. No gaps.

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 has 100% description coverage (include param described). Description adds value by explaining why include is useful: 'needed to wire alerts when creating a monitor.' This goes beyond the schema's description.

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?

Description clearly states 'List all Drumbeats projects...' with specific verb and resource. It mentions what is returned (id, name, plan, basic metadata) and distinguishes it from siblings like create_project or list_monitors by focusing on listing projects for finding target ids.

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?

Explicit advice: 'use it to find the target project id before creating or querying monitors.' Also explains when to pass include parameter: 'Pass include=["channels","groups"] ... needed to wire alerts when creating a monitor.' This tells the agent both the primary use and optional extension.

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