phabricator_build_command

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

No annotations provided. The description says 'send a command' but does not disclose if it mutates state, requires special permissions, or has any side effects. It lacks detail on behavior beyond the action.

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?

Single sentence, no fluff. Clearly states the core purpose and optional payload. Efficient and well-structured.

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?

Missing output schema, response details, error conditions, and prerequisites. The description is adequate for a simple send command but not comprehensive given no annotations.

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 coverage is 100%; all parameters have descriptions. The description adds only a summary of status types and optional results, which is already clear from the schema. No new meaning beyond what the schema provides.

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 clearly states the tool sends a command to a Harbormaster build target and reports status with optional unit/lint results. It uses a specific verb and resource, and distinguishes from sibling tools like phabricator_build_search.

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 for reporting build status, but does not explicitly state when to use this tool vs alternatives like phabricator_buildable_search. No when-not or exclusion criteria are given.

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