hubspot_status_report

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

Annotations already disclose readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the description does not need to restate those. It adds useful scoping context by explaining that execution routes through the domain-agent dispatcher under JWT/tenant/company scope. It does not give extra detail about what side effects the destructive status_report action may have, but the annotation already carries that warning; the description does not contradict 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 front-loaded with the action to run, followed by one scoping sentence and a compact Args block. There is no redundant filler, and every line 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?

Output schema exists, so return values do not need describing, and the optional parameter semantics are covered. However, the description never clarifies what the status_report action actually does or when to choose it over the many related HubSpot and dispatch tools, so an agent selecting among siblings gets only the name and scope as cues. Given the simple optional-parameter surface, this is adequate but not complete.

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 schema has 0% description coverage, so the Args block is the only semantic source. It defines message as 'free-text objective' and inputs as 'Optional JSON string of structured inputs', which adds real meaning beyond the bare string types and defaults. It could be stronger with examples or allowed input keys, but it is sufficient for a two-parameter optional-input tool.

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 a clear verb+resource: 'Run the hubspot domain agent action `status_report`.' This tells an agent exactly what to invoke and ties it to the HubSpot domain rather than a generic status-report sibling. It does not explain what the status report contains, so it falls just short of a 5.

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?

No when-to-use guidance or alternatives are given. The description only notes that the call routes through the platform's domain-agent dispatcher under JWT/tenant/company scope, which explains context but not when to prefer this tool over hubspot_chat, hubspot_plan_domain_intelligence, or the other domain-agent tools. An agent must infer the use case from the name alone.

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