contentrain_submit

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

The description reveals the push behavior and boundary (contentrain/* branches). Annotations indicate idempotentHint=true, which is consistent with normal push semantics. No contradiction, though force push behavior is not clarified.

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?

Two concise sentences with no redundant information. The purpose and key guidance are front-loaded.

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 simple push tool with two optional parameters and no output schema, the description is adequate. It could mention return value or error states, but the low complexity makes this acceptable.

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% with descriptions for both parameters. The description adds the crucial 'contentrain/*' pattern context for branches, but does not elaborate on the 'message' parameter beyond 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 specifies the action 'Push', the resource 'contentrain/* branches', and the destination 'remote'. It clearly distinguishes from siblings like contentrain_branch_delete or contentrain_merge by stating 'MCP is push-only'.

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?

Explicitly instructs not to manually push or create PRs, and clarifies that PR creation is handled by the platform. This provides clear context on when to use the tool versus alternative actions.

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