salesforce_status_report

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

The description adds scoping context (JWT, tenant, company scope) and notes the domain-agent dispatcher routing, going slightly beyond the annotations. However, the annotations mark destructiveHint=true while the name and description suggest a benign status report, and no side effects are disclosed.

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 compact and front-loaded: the main action is stated first, routing/scope follows, and the two parameters are documented with brief but useful labels. There is no redundant or filler content.

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 two-parameter wrapper with an output schema, the description is adequate but not complete. It still lacks guidance on when to use this tool over the many other Salesforce reporting tools in the sibling list, and it never clarifies what a status report provides.

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?

Schema description coverage is 0%, so the description must compensate. It does define message as 'free-text objective' and inputs as 'optional JSON string of structured inputs', but these are still generic and do not explain what content the action expects or how the parameters relate to a status report.

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 specific verb and resource: 'Run the salesforce domain agent action status_report'. It clearly distinguishes the Salesforce domain from sibling status-report tools like hubspot_status_report, though it does not explain what the status report contains.

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?

There is no guidance about when to use this tool versus alternatives such as salesforce_run_report, salesforce_get_pipeline_report, or salesforce_pipeline_report. The only contextual detail is routing, which does not help an agent choose between related reporting tools.

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