it_ops_project_ops

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

The description adds useful routing and scoping context: it goes through the platform's domain-agent dispatcher under JWT, tenant, and company scope. The annotations already declare destructiveHint=true and readOnlyHint=false, and the description does not contradict them, but it also doesn't disclose what kinds of side effects project_ops may cause.

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 with the tool's main action, followed by routing context and an Args section. It avoids unnecessary prose, though a short usage note would have made the structure more complete.

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?

The output schema exists, so return-value documentation is not required, but the description still leaves major gaps: what project_ops does, what 'structured inputs' should contain, and when to choose this over the generic dispatcher tools. Given the enormous sibling list and the opaque action name, this is not sufficient context for confident selection.

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 gives one-line explanations for both parameters: 'message' is a free-text objective and 'inputs' is an optional JSON string. These are helpful but vague, with no examples, expected structure, or hint about how the two parameters interact.

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 a specific action: 'Run the it_ops domain agent action project_ops.' This identifies the resource and distinguishes it from other it_ops tools. However, it doesn't explain what 'project_ops' actually does, so the purpose is clear only at the level of 'this is the project_ops action wrapper.'

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 guidance is given about when to use this tool versus alternatives such as dispatch_domain_agent, invoke_tool, or other it_ops actions. The description does not state use cases, exclusions, or conditions that would help an agent choose this tool over its many siblings.

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