REP Helper

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

With no annotations provided, the description carries the full burden. It discloses that trip association adds travel time to duration and that files come from the local filesystem, but omits mutation side effects, validation behavior, draft vs. final persistence details, and error handling.

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?

Three sentences with zero waste: sentence 1 states the core action, sentence 2 provides domain context, and sentence 3 highlights critical optional behaviors (trip duration handling, file attachment). Information is front-loaded and every clause earns its place.

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 100% schema coverage and 15 parameters, the description appropriately focuses on high-level domain context and special behaviors rather than enumerating parameters. It adequately covers the tool's purpose for a complex IRS compliance tracking operation, though it could explicitly state this is a persistent write operation.

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?

While the schema has 100% description coverage (baseline 3), the description adds valuable domain context: 'IRS REP qualification tracking' explains the semantic purpose of isQualifying, isMaterialParticipation, and irsTest parameters collectively, and emphasizes the 'local filesystem' constraint for evidence files.

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 opens with the specific action 'Log a new real estate activity (hours entry)' and clearly identifies the domain purpose (IRS REP qualification tracking). It distinguishes from siblings by emphasizing creation/logging versus update, delete, or list operations.

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 through domain-specific terms (IRS REP tracking) and optional features, but lacks explicit guidance on when to use create_activity versus update_activity, or prerequisites like requiring an existing propertyId.

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