hcp_get_business_profile

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds valuable context beyond these: that no data is read from or sent to Housecall Pro or anyone else, that an empty profile is normal for fresh installs, and that sections carry confirmation dates.

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 three sentences, each earning its place: content overview, usage guidance, and privacy/edge-case behavior. It is front-loaded with the core read action and then provides necessary context without fluff.

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 no output schema, the description adequately explains return semantics (missing_sections, section dates) and covers data locality and empty-profile handling. It offers a complete mental model for an agent to decide when and how to 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 0 parameters, so the baseline is 4. The description compensates by explaining what the returned structure contains (missing_sections, sections with dates), which is helpful in the absence of an output 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 uses a specific verb 'Read' and identifies the resource as 'the business profile stored for this installation', clearly distinguishing it from siblings like hcp_set_business_profile. It enumerates profile contents (pricing rules, payroll rules, etc.), making the tool's purpose unambiguous.

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 gives clear context: 'Skills read this before asking setup questions' and explains that missing_sections indicates what a first run still needs to ask. It does not explicitly name alternative tools or state when not to use it, but the occasion is well-defined.

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