REP Helper

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

Annotations declare readOnlyHint=true, so safety is covered. Description adds valuable ordering behavior ('ordered by start time (newest first)') not found in annotations or schema. However, it omits details about return structure, default behavior when no filters applied, or pagination beyond the limit parameter.

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, front-loaded with purpose. Every sentence earns its place: defines resource, specifies ordering behavior, and summarizes filtering capabilities. No redundant or wasted text.

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?

Input schema is fully covered (100%), but lacking output schema means description should compensate for return value structure. It minimally states 'Returns activities' without field details. Adequate for simple list operation but gaps remain regarding response format and explicit sibling differentiation.

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 100% schema description coverage, baseline is met. Description lists filterable fields but doesn't add semantic depth beyond the schema (e.g., no explanation of parameter interplay or that all parameters are optional).

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?

States specific verb 'List' and resource 'real estate activities (hours entries)' clearly. Distinguishes from property-related siblings by specifying 'activities', though it doesn't explicitly contrast with 'get_activity' (single item retrieval vs. list).

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?

Implies usage through filter descriptions ('Filter by property, date range, or category'), but lacks explicit guidance on when to choose this over 'get_activity' or whether filters are optional. No mention of prerequisites or when not to use.

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