Andru Revenue Intelligence

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation with flexible data. The description adds valuable context about what gets checked (sync status across three specific platforms) and the tool's diagnostic nature, which goes beyond the 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?

The description is perfectly concise with two sentences that each earn their place: the first establishes the purpose and value, the second specifies the scope. No wasted words, and the most important information is front-loaded.

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?

For a zero-parameter read-only tool with openWorldHint, the description provides sufficient context about what it checks and why. The main gap is the lack of output schema, so the description doesn't specify what format the status information will be returned in, though this is partially mitigated by the clear purpose.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately explains that no inputs are needed for this status check, which aligns perfectly with the empty input schema.

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 with specific verbs ('shows', 'checks') and resources ('CRM', 'sync status across HubSpot, Salesforce, and Pipedrive'). It distinguishes itself from siblings by focusing on data freshness verification rather than scoring, profiling, or triggering actions.

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 context ('whether your CRM has your current intelligence or is running on stale data'), suggesting it should be used when data accuracy verification is needed. However, it doesn't explicitly state when not to use it or name specific alternatives among siblings like 'trigger_syndication'.

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